Dave Nottage

Your intent-filter node is missing from the manifest. The activity node should look like this: <activity android:name="com.embarcadero.firemonkey.FMXNativeActivity" android:label="MixPDV" android:exported = "true" android:configChanges="orientation|keyboard|keyboardHidden|screenSize" android:launchMode="singleTask"> <!-- Tell NativeActivity the name of our .so --> <meta-data android:name="android.app.lib_name" android:value="MixPDV" /> <intent-filter> <action android:name="android.intent.action.MAIN" /> <category android:name="android.intent.category.LAUNCHER" /> </intent-filter> </activity>

Did you set the option to generate 32-bit and 64-bit binaries in the Project Options?

If the breakpoints are not disabled - ie like this: Then the code isn't being reached. Yet when you removed that part, the code in unit main executes? This is where a reproducible example would help.

There's a difference between a breakpoint being disabled (which is indicated visually), versus one where the debugger does not stop. The latter can happen because the code where you have the breakpoint is never reached and/or you have a unit with the same name, and you're looking at the wrong one. Something specific to the platform. Detailing what you have in your datamodule might help (eg. data components used, what type of connection e.g SQLite, etc)

So the problem is with the datamodule. Still? The screenshot you showed in an earlier message indicates they were not. Are you compiling for Debug?

It's not advisable to have conditionals in your .dpr because the IDE can be prone to mess it up. In this case, the conditional for the Android unit is pointless anyway, since nothing from it is being referenced in the .dpr. This would not be the cause of your issue, but it's still something to consider. As @programmerdelphi2k inferred, it may be being caused by something happening in untDataModule. You could use the debugger to see what is executed there when it is created. Has it ever run OK on iOS? Either way, you could remove parts of the application that were previously added, to help isolate what is causing the lockup.

You would have needed to have downloaded your developer profile, so I was assuming you knew how already.

You need to create an Application ID (on the Apple Developer site, this is Identifiers), In general, you won't need to select any entitlements unless you plan on having Push Notifications in your app, in which case select that entitlement from the list For Description, use a description about your application (e.g. just the name), and for Bundle ID, the convention is to use a domain you have, in reverse, then the name of the application. The Description and Bundle ID pictured are just examples. You will also need a Provisioning Profile (in Profiles) for App Store:

This demo starts/works OK on my Pixel 6 Pro, which has Android 13. I'm using Delphi 11.2 with Patch 1 installed. https://github.com/Embarcadero/RADStudio11Demos/tree/main/Object Pascal/Multi-Device Samples/Device Sensors and Services/Address Book/Contacts

Which version of Delphi are you using? Which version of Android is on the device? Have you tried running the app via the debugger to check whether there's any errors?

You execute them from the machine that is connected to the device. adb is in the platform-tools folder of the Android SDK

There's no instruction there to reinstall Delphi.

Please see: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries

Do you have a Provisioning Profile for App Store?

See:

I think you mean Provisioning Profile, but given your comment here, you have resolved that now?

Have you installed PAServer? Please refer to: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Installing_the_Platform_Assistant_on_a_Mac ..and: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/IOS_Mobile_Application_Development

One way would be to have a real device. What is the reason for wanting to test specifically on that? You should not need to.

You could at least post the code for whatever the method is that starts with "ProcessH", as per my earlier comment. You provided a screenshot and said that is where the problem occurs.

Then the problem is not actually happening inside that procedure (though the root cause may be there). The problem is occurring in a method in the Http unit, in a class called TTCPHttpThrd in a method with a name starting with "ProcessH", but the rest of the callstack window is cut off in your screenshot

As long as the PAServer is exposed to the "outside world" (perhaps by port forwarding), yes.. that is possible. Bear in mind however that if you're deploying to a device, the machine that has PAServer on it needs to be able to access the device, either by being connected directly to that machine, or possibly using something like this: https://www.net-usb.com/

I doubt that error message (platform architecture issue) is related to the API level issue. It's possible that you're compiling for 64-bit and the installed OS is 32-bit. Be aware that some devices have a 64-bit CPU, but have a 32-bit Android OS installed.

It may help to delete everything in the output folder(s) in question - by default they're Android/Debug (or Release) and Android64/Debug (or Release), then rebuild

The error message: java.lang.ClassNotFoundException: Didn't find class "androidx.core.content.FileProvider" Usually means that the jar that contains the class androidx.core.content.FileProvider was not included in your app. This class is in core-1.5.0-rc02.dex.jar, and should appear in the Libraries node, as per the instructions in my earlier reply. This is an example of what it should look like: i.e. the package in question does not have a red "x" in the icon

It's odd that you would receive that error on one device and not another. Regardless, please see this: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidLibraries