stewag64

I also had this problem with an earlier version and with 11.3 CE. I have the impression, that dcciosarmxxxx.dll is sometimes not installed on PCs, where several earlier Delphi versions have been installed previously. The solution that always worked for me is to install a fresh Delphi on another PC where there has not been a Delphi installation before. With iOS platform, of course. It need not be the Trial, can also be CE. Then simply copy the dll.

I have a strange problem with a TMapview: Map and markers are displayed perfectly okay if compiled in "Developer"configuration, but when I compile an aab file for Google Play, the TMapview stays completely empty. Only the Google logo and the zoom buttons are displayed. I know that this is usually a sign for a wrong API key, but as the developer version works, with the same settings, it must be something else. As a workaround, I set "Application restrictions" from the package name and SHA-1 fingerprint of my app to "None" in Google API Console and instead added an API restriction on "Maps SDK for Android". Does anybody have an idea what might be the cause for this "split-behaviour"? Steffen

I thought this flag would be checked by default since 10.4. It wasn't?

64 Bit. When compiling for the store, Delphi automatically creates a bundle (.aab) that includes also the 32 bit version, if exists.

Yes, you need also 32bit platform in order to target older devices.

... and make sure your app bundle includes both 64 AND 32 bit platforms.

How many devices?

My idea of generating a special compatibility .apk for older devices does not make sense and was caused by a substantial misunderstanding. See details here:

Thank you, Dave! Changing %minSdkVersion% value in AndroidManifest.template.xml in combination with adapting NDK settings as per your (quoted) article increased the number of supported devices greatly! I tried platform android-19 fist, but that threw an error, so I settled with android-21. It should be stressed that changing only %minSdkVersion%, as suggested by Philipp, does not do the job, as this "fakes" an environment which strictly doesn't exist. My substantial main error though was, that I deleted target platform Android 32 bit from project manager in app version 2.10, caused by my misunderstanding of Google's policy, that apps have to support 64 bit from last August on. That does NOT mean, that app bundles should not also include a 32 bit package! Older devices obviously only accept 32 bit apps. Now, with re-installed Android 32 platform and android-21 NDK platform settings, I am back to 17.463 devices. 🙂

Thanks, Dave, for pointing out the importance of NDK! I tried in vain with "android-19" configuration as mentioned in the article, but was successful when I generated a 32 Bit version. It could be installed by older devices that would not accept a 64 bit version. The major problem and cause seems to be the massively reduced device compatibility that I observed just now between Delphi 10.3.3 and 10.4.2:

I just observed that my Android app suffered a MASSIVE decrease of compatible devices after a new release with 10.4.2, compared to 10.3.3. Please see attached screenshots from Google Play's "Release Dashboard": App bundle 2.9.3.1 (compiled with Delphi 10.3.3. CE) was still compatible with 18.885 devices. 10 month later, I released an update with Delphi 10.4.2 CE which was only compatible with 6702 devices! Do you experience the same with your apps? Or what do you do to maintain device compatibility? Does SDK version has something to do with it? Please note also file size. In order to satisfy users, that could not install the newer versions, I compiled a 32 bit .apk and placed it on my website. It does the job but that cannot be the solution.

I have developed a free application with Delphi 10.4.2 CE for both Android and iOS which is in both Google Play and App store for two years now. Older android phones though can not load the current version, as they are not compatible with latest SDK - and maybe other reasons. BUT: I observed that several smartphones, that are not compatible with the latest version, ARE compatible with an older version that I compiled with Delphi 10.3! The older version was compiled for API level 19+, the consecutive (incompatible) versions were compiled with API level 23+. Both target at SDK 29. I find this quite astonishing, as it means that a phone's hardware is not (always) the restricting part and therefore can be overcome. In order to make use of this, I want to give these older smartphone users the possibility to load and install the latest version of the app by means of a "backward-compatibility" .apk that they can download directly from my website. Therefore, I "downgraded" the SDK & NDK from 10.3 (on another machine) under 10.4.2. Still, the so compiled .apk can still not be installed on my older smartphone (which is the same one that CAN digest the earlier .apk I downloaded from my Google Play developer account). I was lucky to find these 10.3 SDK and NDK on an old image, as 10.3 CE had to be deleted when installing 10.4 CE. I presume that the idea of older-smartphone-participation might attract also others? Who can come up with a workable way to compile for older platforms with newer or latest Delphi?