Dave Nottage

Never mind - it looks like it's an additional problem: https://developer.apple.com/forums/thread/689377 Delphi is not including the information mentioned in that thread. Yet another thing to work around 😞 More later when I work out what needs to be added

Was the profile that you included (as embedded.provisionprofile) the App Store provisioning profile?

That doesn't match this pattern: https://developer.android.com/training/sharing/receive#update-manifest I suggest also reading the rest of that page in regards to handling the incoming intent

According the code, they're supported on at least Android. Check the FMX.InAppPurchase.Android unit. Not sure about iOS. The current implementation for Android was updated after that article was written.

You need jdk-11.0.14.101-hotspot. You could use Tools | Manage Platforms, and select Additional Options in the IDE to install it, then configure your Android SDKs in the SDK Manager in Delphi to modify the settings on the Java tab. Once you have that right, see: https://github.com/DelphiWorlds/HowTo/tree/main/Solutions/AndroidServiceDelphi111

One that supports the latest version of iOS, if possible. It appears this is iPhone 7. That said, the support for later iOS versions for that device might soon disappear. See here: https://docwiki.embarcadero.com/RADStudio/Alexandria/en/IOS_Mobile_Application_Development That's usually not a requirement, however there might be some specific arrangement they're referring to that I'm unaware of. The only cost should be for the Apple Developer program

Apparently things are different on Android 11 or higher: https://developer.android.com/training/articles/user-data-ids#mac-11-plus Going by that documentation, it appears it is not possible any more. If you're after a unique identifier for the device, see the earlier messages in this thread.

I never assumed anything like that. What is missing from his post that raises that question?

Check the links in his post

Because it doesn't officially, yet. That is not to say apps will not work on it - in fact, they can, and do Yes, this is often a source of much confusion. The installed SDK "version" and installed API levels and build tools do not necessarily directly relate to whether an app will work on a particular version of Android. There are some considerations to allow for to support Android 13, outlined here: https://developer.android.com/about/versions/13/migration. There's also been a number of questions here and on Stack Overflow about how to deal with some of them

If you're after something that does both (generate the doc, and parse it), there's this: https://github.com/paolo-rossi/OpenAPI-Delphi

The error message in the image says: " ',' or ':' expected, but identifier 'iOSapi' found..". You need to look at the code that comes before it, which you cut off in the image

Except you do not say what the actual problem is. Your code compiles OK here.

It's an iOS "quirk". It caches launch images for 24 hours. One way to fix it immediately is to change either the project name or CFBundleIdentifier value

Yes.. it supports Android and iOS

Looks like it still has some learning to do

This is the code: unit utTFrameStandDemoLoginFrame; interface uses System.SysUtils, System.Types, System.UITypes, System.Classes, System.Variants, FMX.Types, FMX.Graphics, FMX.Controls, FMX.Forms, FMX.Dialogs, FMX.StdCtrls, FMX.Controls.Presentation, FMX.Objects, FMX.Effects, FrameStand; type TTFrameStandDemoLoginFrame = class(TFrame) TFrameStandDemoLoginFrameRectangle: TRectangle; TFrameStandDemoLoginFrameToolBar: TToolBar; TFrameStandDemoLoginFrameToolBarShadowEffect: TShadowEffect; TFrameStandDemoLoginFrameToolBarLabel: TLabel; TFrameStandDemoLoginFrameToolBarBackSpeedButton: TSpeedButton; procedure TFrameStandDemoLoginFrameToolBarBackSpeedButtonClick(Sender: TObject); private { Private declarations } [FrameInfo] FInfo: TFrameInfo<TTFrameStandDemoLoginFrame>; public { Public declarations } end; implementation {$R *.fmx} procedure TTFrameStandDemoLoginFrame.TFrameStandDemoLoginFrameToolBarBackSpeedButtonClick(Sender: TObject); begin FInfo.HideAndClose; end; I expect it's because FInfo is not being created

I think you mean info.plist.TemplateiOS.xml

You'd need to have PAServer on your MacBook accessible from the VM. Since the VM is outside of your work environment, you would probably need to set up port forwarding on your router, so that it can forward to PAServer.

It's because of this issue: https://quality.embarcadero.com/browse/RSP-40302 Workaround steps from the report: Locate the matching App Store provisioning profile on the Mac Copy the provisioning profile to the project folder, and rename it embedded.provisionprofile Add embedded.provisionprofile to the Deployment for macOS, with a Remote Path value of: Contents\ Deploy Now the app should be able to be submitted to TestFlight

Yes, it's possible to run apps on Android 10 using Delphi 11.2

I have the same setup as you and it works OK. On the Mac, can you open a Terminal window, execute this command: /usr/bin/xcodebuild -version -sdk If it succeeds, the results can be fairly lengthy, but you should see things like: MacOSX13.0.sdk in it

Anyone here successfully deployed a macOS App Store application? I've followed the instructions here: http://docwiki.embarcadero.com/RADStudio/Rio/en/Completing_the_Provisioning_Page ..have a correct provisioning profile on my Mac, and have set CFBundleIdentifier to the correct value, however Delphi complains: [Error Error] Missing provisioning information. Mobile Provisioning Profile has not been specified for the "AppStore" platform configuration. Any ideas as to what I should check?

Yes, by having the correct provisioning profile for App Store that matches the CFBundleIdentifier value in the Version Info page of the Project Options, and by specifying the correct certificate information in the Provisioning page of the Project Options.

It's possible that the app is installed for another user, in which case the form of adb uninstall will need to be: adb uninstall 'some.package.name' Where 'some.package.name' is the package identifier, e.g. com.embarcadero.FMXClock. This form of the command will uninstall for all users