Dave Nottage

Using a URL I can reach, the code works fine for me

Your example code does not have any calls to Assign or Reset. Having said that, why are you using long deprecated file access methods? TStringList has LoadFromFile and SaveToFile methods. It might help to show an example that focuses just on GetDocumentsPath and the file access parts, if that's what is failing

I had not actually read Chris' article - I was aware of most of the process, however I did not realise the issues regarding building for App Store. That puts a whole new slant on things. I'd like to be able to automate as much as I can (via Codex/Mosco) That's great! I'm sure to need testers and feedback.

Looking at the differences in the source code for FMX.InAppPurchase.Android.pas between Delphi 11.3 and 12.1, I'd say yes.

Yes... ...if by: "image in the payload", you mean: "a url to an image in the payload" As inferred in the earlier messages, doing so in a Push Notification is possible only by using an App Extension (in this case, a Notification Service extension) which needs to be an Xcode project. I've been ruminating over the best way to make the process as painless as possible, by providing a template Xcode project of which hopefully only a couple of properties need to be changed to match the Delphi project. As with other projects that require the user to follow a bunch of steps to integrate the solution, I'm apprehensive over the number of inevitable enquiries as to how to make it work.

I'm unable to reach that URL at all.

Now I can reproduce the problem. Might be to do with the number of controls and/or alignments. I suggested reporting the bug.

Using the arrangement you described, I am still unable to reproduce this.. ..using the same version of Delphi.

Please keep the profanity out. Delphi treats the constant in that statement as a set. See this.

They may mean in the Project Options - these are the defaults:

I tried reproducing it using your steps, and was unable to. What version of Delphi?

Yes, as I've used CocoaPods to download SDKs before. It will be easier though if they have a direct download of their SDK. Which SDK is it?

Possibly, via Tools | Manage Features: Ensure the OpenJDK is installed. (right hand side, scroll all the way down). If it is not, select it, and click Apply. Deselect the SDK/NDK, and click Apply Reselect the SDK/NDK, and click Apply. During these steps, you might need to re-open Tools | Manage Features. I can't remember if it closes after clicking Apply.

I suspect the Android SDK was not installed completely. Check the SDK settings (Tools | Options > Deployment > SDK Manager)

Works OK here. Either there's an issue with your device, or you need to provide more information, e.g. Are there any error messages when it crashes? Where in your code does it crash? Have you used a log viewer to check for error messages and if so, are there any? Is there any other relevant code you've left out in your post?

Did you read the reply from bzwirs?:

Your screenshot looks very much like it is from an emulator I don't know, because you never really answered this question: No - it is built direct from the demo app, with no alterations, using Delphi 12.1

Does this happen also on a real device? Regardless, do any of these answers help?

Posted a 64-bit APK built with Delphi 12 here.

Yes, it is a matter of that. It's explained in the demo in Kastri.

You could use GetMousePos to check if the mouse is inside of it, like this: uses FMX.Platform; procedure TForm1.ParentPanelMouseLeave(Sender: TObject); var LService: IFMXMouseService; LPoint: TPointF; begin if TPlatformServices.Current.SupportsPlatformService(IFMXMouseService, LService) then begin LPoint := ScreenToClient(LService.GetMousePos); if not ParentPanel.AbsoluteRect.Contains(LPoint) then ParentPanel.Fill.Color := $FFE0E0E0; end; end;

Is this using the demo, unaltered, following all of the instructions? In which version of Delphi?

Hopefully all sorted now, including: Added new API import DW.Androidapi.JNI.AssetDelivery.pas Added new jar files to the ThirdParty\Android folder in Kastri Updated DW.AssetDelivery.Android.pas Updated the demo, including the manifest template. Updated the batch files which are included with the demo, to account for the changed Android build process in Delphi 12.1 Updated Codex to also account for the changed Android build process in Delphi 12.1 As you may have guessed, it wasn't as simple as swapping the .jar file, especially since asset-delivery-2.2.2.jar is dependent on play-core-common-2.0.3.jar. Newer versions of Android also require this implementation to have the Foreground Service Data Sync permission. I am yet to test with an AAB that's actually on Play Store (whether internal or not), but "local" testing worked OK.

As far as testing goes, so far this has not progressed well - the build process has changed which means the automation in Codex has broken, as well as the BuildBundle batch file that is provided with the demo. More later...

I have done a more detailed check now (I had not when I sent the first message), and I can see that the classes/methods are all compatible and the namespacing of the classes is identical, so removing the old jar from the project and adding the new one should work, but I'll know for sure when I do a test, hopefully before the end of the weekend.