I understand you got some help from our Support engineer to resolve this issue. Here are some comments for others who may have a similar issue working with IBToGo 2017 on Mobile (iOS/Android) from RAD Tokyo.

If you are a customer downloading InterBase 2017 IBToGo kit from GetIt repository for RAD Studio, you will need to execute a couple of manual steps to make IBToGo 2017 work for Mobile platform deployment. Since IBToGo 2017 is not automatically installed by RAD Tokyo (yet), these steps are necessary to be done manually.

In the downloaded image for IBToGo 2017 zip file...

• Extract libibtogo.a from ios_device.zip to both the lib\iosDevice32\debug and the lib\iosDevice32\release folders within your RAD Studio install.
• Extract libibtogo.a from ios64_device.zip to both the lib\iosDevice64\debug and the lib\iosDevice64\release folders within your RAD Studio install.
• Extract libibtogo.a from android_togo.zip to both the lib\android\debug and the lib\android\release folders within your RAD Studio install.
• rebuild and deploy your app to iOS/Android device.

www.embarcadero.com/support

Read More...

Thanks for working on cleaning up your installation and giving it another try. We will get to the bottom of this. :-)

ibbbtogo.slip is not required to be packaged with your application. This is just a template license file that we ship with the product. You can safely remove this from your Project Deployment list.

To switch between IBLite and IBToGo, the FireDAC driver ID setting seems to be just "IBLite" as per http://docwiki.embarcadero.com/RADStudio/Tokyo/en/Connect_to_InterBase_(FireDAC). The actual switch happens based on the license file you deploy with the application (as per your Project Deployment setting).

Say, you have 2 license files that you have registered and downloaded; reg_ibtogo.txt and reg_iblite.txt. Please make sure these files are delivered to C:\Users\Public\Documents\Embarcadero\InterBase\redist\InterBase2017 before you build/package your application in RAD Studio. Mention both of these in the Project Deployment list, but enable/select only the one (IBToGo or IBLite) license that you want included in your application. If you include both, then InterBase will pick and use IBToGo license over IBLite.

I think the problem could possibly be related to the license file itself that you have. You may want to connect with Embarcadero Support and have them validate the license file you have. If you don't get a response within a day or 2, please have them send the license file to me and I can escalate it for validation.

Good luck!

Read More...

Just so you know, RAD Studio 10.2 Tokyo does not install IBToGo 2017 version automatically. The IBToGo version installed is XE7 version. If you want to use IBToGo 2017, I assume you have been informed (community.embarcadero.com/blogs/entry/in...-update-1-and-delphi) about how to GetIt from the repository.
If you have done the above, the IBToGo 2017 ToGo Test Deployment license should be registered following instructions at http://docwiki.embarcadero.com/RADStudio/Berlin/en/IBLite_and_IBToGo_Test_Deployment_Licensing#IBToGo_Test_Deployment_Trial_License

You *must* deliver the newly downloaded license file from above, so your Project Deployment file list includes this in the packaging for all platforms; in your case, Windows and Android. Once you do this, the IBToGo 2017 library you use will be able to utilize the license file properly. I wonder if your application is currently bundling (erroneously) IBToGo XE7 files with a IBToGo 2017 license file.
Currently, it works on your Windows development machine because RAD Studio 10.2 on the development box comes packaged with both IBToGo XE7 and IBToGo 2017 license bundled. When you run your application (in this faulty bundling) on a Android device, the license mismatch causes the behavior, I think.

Read More...

I am assuming you are using either InterBase XE7 or 2017 version.
Do you have any environment variables defined for INTERBASE or IB_PROTOCOL when running your application? If yes, unset INTERBASE environment variable, and just set IB_PROTOCOL to your InterBase instance (perhaps 'gds_db').

Do you have other InterBase servers/instances running on the same machine?

Read More...

Which version of InterBase IBToGo are you using on your development machine? XE7 or 2017?
How did you register your IBLite and IBToGo Test Deployment S/N? Did you use the instructions for IBLite license registration documented at http://docwiki.embarcadero.com/RADStudio/Tokyo/en/IBLite_and_IBToGo_Test_Deployment_Licensing? Make sure you are using a XE7 license S/N if using IBToGo XE7 s/w. This license file will allow you to install on all platforms where IBToGo can run without limits on deployment.
Once you downloaded the license file from registering above, have you been able to deploy the application to a PAServer on some Windows machine? This will validate that the license file and packing are all good. Then, it is a matter of validating the files packaged and deployed to Android.
Which version of Android are you deploying to? Which device? I am assuming only 32-bit.

Read More...

Glenn,
I assume you are using RAD Studio XE8 or an equivalent Delphi/C++/Appmethod version to build and deploy your Mac OS X application to the Apple Store.

The Container location can be specified in your Project Deployment file list; mark your database file to go to Contents\Resources\StartUp. The RTL code will automatically copy your database file from the package (at application startup once) to the newly created Container location for your application.

Further details at docwiki.embarcadero.com/RADStudio/XE8/en...Mac_OS_X_Application

The same applies to any InterBase database files should you choose InterBase over SQLite; docwiki.embarcadero.com/RADStudio/XE8/en...se_ToGo_for_Mac_OS_X

Best wishes,
Sriram
Read More...

Balint,
Have you enabled .NET 2.0 on Windows 8? If not, you can do this by following windows.microsoft.com/en-us/windows-8/net-framework-windows-8. Here is a sample InterBase ADO.NET app setup as well... blogs.embarcadero.com/stephenball/2015/0...-from-visual-studio/

Also, InterBase 7.x has not been tested or certified on Windows 8; so, your mileage may vary. You may want to upgrade to InterBase XE7 for Windows 8. You can find the latest InterBase features detailed at www.embarcadero.com/products/interbase

Best wishes,
Sriram
Read More...

Omar,
Are you able to do a full "Server and Client" install instead of the just "Client only" option?
Read More...