Hans♫

Excellent point! - You are right, I just typed in a file name without specifying the path, and that was the reason. After having specified a destination filename WITH path, it works fine! Thank you for pointing me in that direction.

Thank you for your persistence Dalija. I have a heart for Delphi too, and I somewhat regret that I posted the image, because I still have no proof if it is our code or Delphi code that fails. With the graph I am basically bashing 10.3 RIO because I am tired of its quality. Our database access uses exactly the same code on Windows, Mac and iOS. No crashes detected or reported on Windows and Mac. But as you said, iOS is just waiting for a reason to take your app out. It is a lot more strict on everything.

I investigated all recent crash reports delivered to XCode for the app. The majority of the crashes contains a reference to a sqlite file in our app and "Code 0xdead10cc", which means "terminated by the OS because it held on to a file lock or sqlite database lock during suspension" The positive news is that the user will not discover the crash because it happens when it enters suspension state anyway.

Ha, ha, we only release an update when there is nothing new, nothing fixed and absolutely no change in the code 😉 The graph is no proof, but its an indication.

Its just a screen dump from App Analytics in App Store. I did not make the graph, Apple did: The graph is not a scientific proof that those Delphi versions are the cause of the leaps, but it is interesting that both leaps happened exactly at the same time as upgrading the Delphi version. Except for 10.3 Rio, I am still very pleased with Delphi as it allows us to share 99% of the codebase among the Windows, OSX and IOS versions of our app. BTW, on iOS we are using the native iCL components and not FMX.

Yes, I have the graph by OS also, but in both situations where the the graph stepped up, it happened with the same OS. So that is not the reason.

With Delphi 10.3 Rio, I have added MacOSX SDK 10.14 in the SDK Manager, which I use to build my apps. However, when I run "otool -l <binaryfilename>" on the deployed executable I get this: cmd LC_VERSION_MIN_MACOSX version 10.8 sdk 10.8 This happens also with an empty app. It is a problem because I need to Notarize the app with Apple, and it fails with the reply: "The binary uses an SDK older than the 10.9 SDK". How can I change that?

Now added to Quality Portal that you cannot Notarize a Delphi MacOSX app. I found there is actually another problem too. Please vote for it: https://quality.embarcadero.com/browse/RSP-23368

Thank you for your reply, but in the SDK Manager I can only set the target SDK, which is already set to MacOSX 10.14:

I use ScreenService.GetScreenScale to get the Screen scaling. It was partly broken in 10.2.3, but in 10.3 it seems to be completely broken. In 10.3: No matter what scaling is set in Windows: 150%, 175% or 200%, the return value of ScreenService.GetScreenScale is 1.0. In 10.2.3 it did return the value 1.5 with 150% scaling, but with 175% and 200% scaling it also returned 1.5 I post it here before I post it as a bug in QP, in case I missed something...? This is the function where I use it (and yes it does actually call GetScreenScale): function tScreenScale.GetScreenScale: Single; var ScreenService: IFMXScreenService; begin Result := 1; if TPlatformServices.Current.SupportsPlatformService (IFMXScreenService, IInterface(ScreenService)) then Result := ScreenService.GetScreenScale; end;

Thanks for the demo app. Compiled with 10.3 it gave the same result as previously - until I logged out of Windows and in again, then it worked. Apparently in Windows 10 GetScreenScale returns only the value present at login time, that's why my first experiments did not work. Later I turned on the "Fix blurred apps" setting in Windows 10 and then it returns the correct value immediately even without logging in again. That's great, so Rio 10.3 works! However, when compiled with 10.2.3 it now always returns 1.0, even if I reboot after having changed the scaling in Windows. I am going to figure out why that happens...

It is the same when running outside the IDE.

My Delphi 10.3 Rio installation has no iOS target: SDK manager > Add > Select Platform: There is only Windows and macOS on the list. iOS is not there. Tools > Manage Platforms: shows that iOS target is installed. paserver runs and connects fine on the mac, as I can build and run macOS applications from 10.3 Rio. I have installed MMX, CnPack and Project Magician. What can I do to make the iOS target show up?

Problem solved. It was a license problem. I contacted Embarcadero support and they gave me different serial number for my subscription, which solved. It required me to reinstall 10.3 though.

iOS does not exist as a platform I can choose anywhere in 10.3. Even if it did exist, AFAIK I would still be required to choose an SDK before I could add iOS as a target platform in a project. But I cannot add any iOS SDK at all, as described in my question. Edit: and when I want to add a SDK, I have to choose the platform before I can choose what Connection Profile I want, which leads me to conclude that it has nothing to do with XCode because it doesn't even connect with XCode to check, but maybe the macOS build caused the iOS platform to be removed? Edit2: I tried to build and run an empty iOS app with XCode, then building and running a macOS app with Delphi, but still no change.

Yes, I have a connection profile and it connects fine with paserver. I can build, deploy and run a macOS application.

I have been using the Dproj Normalizer with great pleasure. Its doing a great job to minimize the changes of the .dproj file when committing to version control. However, the latest version does not include 10.3 Rio as an installation target. Is there an update on the way?- or did Delphi include its own solution to make a structured organization of the .dproj file in 10.3 Rio?

Great, thank you. I missed that change of the project.