Chris Pim

I’ve found a link to how to add a storyboard to a Delphi 10.3 project here: https://quality.embarcadero.com/plugins/servlet/mobile#issue/RSP-12931 Take a look at the 4th response from Sarina DuPont

I doubt you’ll be able to use storyboards in 10.3.3 projects but I would be very interested to hear if anyone has found a workaround. In terms of Apple, they won’t remove your app if it’s already approved, they just won’t let you upload new updates or new apps after the deadline. i suggest you report any and all issues you’re having with 10.4 to Embarcadero via the quality portal as they seem to be working quickly to review new bug reports and release patches so that’s the best way to move forwards.

Thanks guys that’s really helpful. I was searching for the NSHighResolutionCapable flag so no wonder I didn’t find that article! I’ll give it a try.

I wonder if anyone else has seen problems with UI scaling on MacOS apps? I created a testing tool in Delphi 10.3.3 for Mac OS and it looks great on 10.15 (Catalina). My MacOS SDK in Delphi is 10.15.3. I passed the binary to a colleague running MacOS 10.13 to run, and although the window size was the same, the contents rendered 4 x larger and the app became unusable. After some trial and error I realised the problem was the NSHighResolutionCapable which was set to true. I changed this to false and it runs fine on both Macs ok. The only remaining oddity is that it renders the titlebar twice - the correct one and then a secondary one with the app name directly below it. I've searched Embarcadero's quality portal for any reference to this but can't find any. Has anyone else had this problem before? I'm happy to log it with them if it looks like a bug. I'm not even sure what having NSHighResolutionCapable = true does besides cause problems, so wonder if I'd be better keeping it turned off?

I’ve checked and there’s an extra key in the registry location you mentioned called JDKPath which isn’t published into the IDE. Changing this seems to have fixed the problem and I can now build an aab file! Thanks again Dave

Thanks Dave. Have you ever had problems with it generating the buildconfig.json file? It doesn’t seem to have created one in my release folder so wonder if I need to turn something on in my project config?

Hi, I've successfully built and tested my app on Android 64 with Rio 10.3.3 and now trying to build the .aab file. The project is configured to build this, but I'm getting an error at Deployment time: [PAClient Error] Error: E6408 java.lang.UnsupportedClassVersionError: com/android/tools/build/bundletool/BundleToolMain : Unsupported major.minor version 52.0 I've always used JDK1.8.0_60 and that's what the paths are in my SDK Manager for Android 32 and 64 targets. The odd thing is that the command Delphi is running is: [PAClient Error] Error: E6408 Unable to execute '"C:\Program Files\Java\jdk1.7.0_25\bin\java.exe" -jar "c:\program files (x86)\embarcadero\studio\20.0\bin\android\bundletool-all-0.10.3.jar" build-bundle --modules="C:\Development\Project\Android64\Release\Project\base.zip" --output="C:\Development\Project\Android64\Release\myShiftPlanner\bin\Project-unsigned.aab" --config="C:\Development\Project\Android64\Release\Project\buildconfig.json"' (Error 1) Where is it determining that it needs to use JDK1.7.0_25? I can't see this anywhere in my Tools > Options? Surely it should be using the one I defined in my SDK Manager? If I manually run the above command but use the 1.8.0_60\bin\java.exe instead, it complains about a missing buildconfig.json file - which is missing from the release folder. It sounds like I may be missing a configuration or something similar? I followed EMBs instructions on the DocWiki to configure my project. Has anyone else had a problem with this or know if there are issues with the bundle tool?

Thanks Dave, I’m glad you saw the same. Thanks for reporting it for me too, I’ve voted for it so hopefully it’ll be looking into.

Hi all, I've been trying to integrate Facebook Audience Network into my Firemonkey app for ads and I'm getting a very strange error when linking for iOS. I use the "fake loader" approach to linking the framework. const libFBSDKCoreKitBasics = 'FBSDKCoreKit-Basics.framework/FBSDKCoreKitBasics'; //required as it's a dependency for the FBAN library libFBAudienceNetwork = 'FBAudienceNetwork-5.2.0.framework/FBAudienceNetwork'; function LibFBCoreKitBasics: Pointer; cdecl; external libFBSDKCoreKitBasics name 'OBJC_CLASS_$_FBSDKURLSessionTask'; function LibFBAN: Pointer; cdecl; external libFBAudienceNetwork name 'OBJC_CLASS_$_FBNativeAdView'; The error when I try to link, is this: ld: file is universal (4 slices) but does not contain a(n) arm64 slice: ..\Libraries\FBAudienceNetwork-5.2.0.framework/FBAudienceNetwork for architecture arm64 I've Googled and the only reference to this kind of error is related to armv7 when trying to link frameworks into a 64bit app that only contain 32bit versions. So I try building a 32bit version of my app in Delphi and see: ld: file is universal (4 slices) but does not contain a(n) armv7 slice: ..\Libraries\FBAudienceNetwork-5.2.0.framework/FBAudienceNetwork for architecture armv7 Which doesn't make any sense! It looks like the FBAudienceNetwork framework is essentially empty with neither 32 or 64bit code which can't be true as it's 1.7Mb and fresh from the official download page. I've tried different versions of the framework but get the same error each time so I've ruled out a corrupted download. I've tried linking through the "Linker Options" in the project settings instead but get the same errors. Linking the FBSDKCoreKit libraries works using the same approach. Does anyone have any ideas or know why I'm getting this error? Thanks in advance!

That’s good news. In terms of the banner being in a scroll box, I’m not surprised that it flickers when scrolling as it isn’t really designed to be used like that. I suggest anchoring it to a fixed position on your form if possible. The flicker is because the FireMonkey code has to recalculate the position when it scrolls and force a re-render of the native control. As FireMonkey isn’t responsible for rendering the banner it can’t use double buffering to smooth the flickering as it would with other controls. Sorry but if you need it to be in a scroll area then I’m not aware of a solution, but maybe someone else does?

The TBannerAd component creates a native control. Because of the way FireMonkey renders everything to a canvas, native components will always render on top of FireMonkey components. It’s a side-effect of the way it works. The way I got round this is to hide and show the banner component when in other screens (e.g. tabs of a page control or frames which display as screens depending on your UI architecture), so it doesn’t get it the way when I don’t want it to. I also suggest including a bottom padding to your multi view menus to push the contents above the banner. I hope this helps

That’s a shame but useful to know. Hopefully we won’t need any hacks!

I wondered the same thing but I guess as the NDA exclusion only mentions allowing Android updates from 10.4 beta not iOS, you’d still be better using 10.3.2 for iOS, Windows and Mac builds while they get 10.4 released if you’re already using 10.3 anyway. 10.3.1 is really buggy so if 10.3.2 is more stable then it may be worth upgrading.

Very true, yet I still have hope that EMB get a 10.4 beta out soon so we can have a proper solution rather than a risky hack!

Reassuring words from EMB about it already being underway. Summer is a long season so hopefully the 10.4 beta program will start sooner rather than later!