Shano

Yes I reinstalled the last official release Xcode 15.0.1 - Oct 18 2023 and all works as expected. Well that only cost me half a day. Thanks.

I have xcode 15.1 installed. I think it is a Delphi Error though, using the incorrect call to the PAClient. I am not trying to run the simulator. I am trying to delpoy to the mac.

M1 I can open the simulator from Xcode. Problem is I do not want to use the simulator. I want to build a Release for submission to Testflight, but everytime I try to deploy the App, for some reason it tries to run the simulator. I just want to reset so that the Release deployment works as it used to, Platforms = (com.apple.platform.iphonesimulator)

Hi, I am using Delphi 12 I decided to try the iOS simulator out which was a huge mistake, because now I cannot deploy my release App. When I deploy Delphi keeps trying to deploy to the iOS simulator it seems. Anyone know how to fix this issue? [PAClient Error] Error: E6664 /Users/MyUserName/PAServer/scratch-dir/MyMac/AppName.launchscreen/Assets: error: The operation couldn’t be completed. Failed to locate any simulator runtime matching options: { I tried deleting all the files in the Scratch directory on my Mac already.

Well I can't seem to get the aab that I submit to Google Play to provide a version for my Android device that is a 64bit device, using a 32-bit mode when submitting a build for testing. I would have thought the Google Play internal Testing area would also use the aab file to create versions of the app that can be installed onto these devices for testing. I understand that to iinstall an APK onto the phone it would need to be built using either the 32-bit target or the 64-bit target. That works. If I build a 32-bit version then I can install the APK onto the 64-bit device using 32-bit mode. That installs perfectly. Just the aab file that I subit to Google Play and then expect to be able to install on the device from the Google Play internal Testing link does not. We also have release the App live and the devices cannot install it onto these devices either and we have the setting correct in the previously submitted aab files as well.

@Dave NottageThat is what I thought. When in development and have a 32 bit device connected, then select 32 bit development and when I have a 64bit device connected select the 64 bit tarket. That works fine. But when I build the App and deploy, creating the .abb file which I then submit to internal testing, using the developer console, and then install the internal testing version on my 32 bit app I receive the message the * "Your Device isn't compatable with this version." * "You're an internal tester. This App maybe unsecure or unstable" Does the Android App Bundle Support only work once the App has been submitted as a live App and is available on Google Play for all to download using either a 32bit or 64bit device? I would have expected the Android App Bundle Support to also work in the Internal Testing side as well.

@Dave Nottage Hi, so is the only way to make sure Android App's developed using Delphi 12, is to build 2 2 separate apps? One targeting the 32 Bit architecture and the other 64 bit Architecture? App - 32, and App - 64 Is that correct? I have the Generate Android 32-bit and 64-bit binaries set to True and when I try to install the 64 Bit onto the device I receive "Your Android device does not support the selected target platform architecture" and I have confirmed that the device is running in 32 bit as you suggested above? Thanks in advance.