futuron

Maybe the following is a proper solution (at least until Embarcadero gets their act together): Scaling issue on macOS 14 (Sonoma) Using Delphi 11.3 (and probably earlier), apps on macOS 14 (Sonoma) may appear to have the wrong scale, depending on the screen resolution. This is an official workaround based on this Quality Portal report. 1. Copy FMX.Platform.Mac.pas from the source\fmx folder and put it in the search path for your project, e.g., the same folder as the project, or add the unit directly to your project in project manager. (Remeber to remove the read-only attribute from the file before you start making any changes). 2. Modify the TMacWindowHandle.GetScale method as follows: function TMacWindowHandle.GetScale: Single; begin if TOSVersion.Check(14) and not GlobalUseMetal then Result := 1 else Result := Wnd.backingScaleFactor; end; This is not mine, I found it on one of the social networks. Normally I would post a link but this forum page flagged it as spam. For that reason I copied and pasted the text.

Still very happy with my MacBook. Compiling for Windows, MacOS, iOS still trouble free. And I could swear it is faster than on a regular native windows machine. Still today I have troubles with connecting my (older) samsung phone to it. I have another regular windows 11 machine and it connects fine there so the culprit is not Win11 but it is Win11 for ARM. Personally I love Win11. I have it installed on every machine I have. However, other than aesthetics I don't see a benefit of Win11. It looks a little more Mac-like so that's probably why I like it better. If you're into dark-mode on Windows then Win11 is definitely better than Win10. The only 2 remaining problems I have with my virtual machine: * getting the Samsung phone to connect normally (culprit is Microsoft's ARM implementation) * getting to run PostgreSQL to run properly (culprit is PostgreSQL does not have an ARM ODBC driver, yet) Everything else, literally everything else works great.

Hi Lars, not sure why you are having problems. I think I have the same setup and mine works like a charm. Compilation speed is totally absurd. My previous dev environment was on a late 2014 Macbook Pro (16GB mem, and additional Nvidia graphics). My new Laptop with an M1 Max processor (32GB mem) is a beast compared to my old laptop (and a beast to any other Windows laptop in our building - lol). Not really fair because having six years in-between, but compared to my home-game computer this this is fast! Real fast! Back to your problem, maybe telling about my setup, and the following order of getting to that setup helps: MacBook Pro 16 (M1 Max processor): macOS Monterey (version 12.0.1) installed Xcode 13 (v13.1) and inside of that I created a few signing certificates (apple development, and apple distribution certificate) Parallels Desktop Version 17.1.0 (51516) Inside Parallels: Installed "Windows 11 Pro Insider Preview" installed (thus ARM version) inside (Build 2250.rs_prerelease.211112-1650) I left everything to standard/automatic (such as CPU&Memory is set to "automatic" on my machine) graphics set to "best for external displays" as I typically run Windows/Delphi on a bit larger external display Inside Startup and Shutdown (options) I changed "on VM shutdown" to "close window" so I don't manually have to close the VM after I shut down windows Coming from VMWare I set several sharing and applications settings such that they mostly matched what I was used to Then booted Windows inside Parallels. Installed Delphi 11 Applied the November Patch Coped PAserver22.0.pkg from "C:\Program Files (x86)\Embarcadero\Studio\22.0\PAServer" to a shared folder inside Parallels so I can access it from my Mac Back to the Mac: Ran "PAserver22.0.pkg" to install PAserver Then ran the just installed PAserver-22.0 app (when I run PAserver it tells me that the version is 13.0.12.1) inside the window, pressed enter (thus not using a password), and then pressed "i" to retrieve the IP address needed in Delphi Back to Windows Started Delphi Inside Tools/Options: Connection profile manager, added host, called it MacOS, gave it the IP address found within PAserver. I didn't touch the port number or the password. The connection should then work properly Once the connection is OK then proceeded to SDK manager and installed SDK manager: added the macOS 64-bit (MacOSX 12.0) SDK, telling overwrite existing files SDK manager: also added macOS ARM 64-bit (MacOSX 12.0) SDK SDK manager: iOS device 64-bit (iPhoneOS 15.) SDK SDK's for android 32 and 64 bit along with windows 10 SDK were already installed with Delphi After that I installed all my regular components The above following-order 100% works, at least for me. So far I've compiled 32-bit windows, 64-bit windows, MacOS 64-bit, MacOS ARM!, and iOS apps without any problems. I can also package both Mac apps and iOS apps for Apple's stores! Probably today I'll try compiling for Android. And for who wonders... compilation speeds are totally nuts from my point of view. This thing is real fast. I will be saving time not having to wait as much for compiling, and packaging apps. Not even mentioning waiting for starting MS office apps (build for ARM) on the Mac-side, or running any other program on the Mac side. I ran Pixelmator the other day, did a "super ML resolution" on an image and I was floored on how fast that went. Sick! This was one of the best investments I've made for our company. Hope this helps

Oh boy... From Apple's website: Submissions Update August 19, 2019 You can now submit apps built with Xcode 11 beta 6 using the SDK for iOS 13 beta 7, tvOS 13 beta 7, and watchOS 6 beta 7 for internal and external testing. Starting with Xcode 11, Application Loader is no longer included in Xcode. For details on how to upload your apps to App Store Connect using Xcode, see Xcode Help. Anyone know if Embarcadero is aware of this? I'm starting to feel very uncomfortable. Again something that could break our workflow! I hope they are on it else I will have to look into starting to develop in Swift and forget about Delphi for the future. Source: https://developer.apple.com/app-store-connect/whats-new/?id=submissionsupdate8-19

Here is temporary work-around: Download an old version of Xcode and installed it next to my new Xcode version. I renamed the new Xcode app into "XcodeNEW". That solves the problem and I've been able to upload since then with out any problems. It's a band-aid that works for now. Howto: * sign-into your developer account at Apple: https://developer.apple.com/membercenter/index.action * look for "Downloads" on the left (below additional resources) * at the very top, just below the page's banner, below the search-icon, click "More" * on the left, deselect everything but "developer tools" * scroll down into the list and find Xcode 10.3 * click on the "+" before Xcode 10.3 and click the zip file. Download the file. * rename your current Xcode into XcodeNEW * unpack and install the downloaded zip file.

Application Loader does not seem to exist anymore. Apple announced this a while back. Unfortunately not seen any response from Embarcadero. That means that we won't be able to publish any app to Apple's app stores anymore until Embarcadero solved this. If you need to publish to the App Store then DO NOT UPDATE!

Has anyone tried to send a MacOS64 app to the Apple App Store yet? Using Application Loader inside Xcode 10.3 on Mojave 10.14.6. When I upload an app to submit it to the store no icon is displayed. The pkg file uploads just fine however checking inside "App Store Connect" (former iTunes connect) the uploaded build also does not have an icon. Apple's shows a question-mark instead. Any idea what I'm doing wrong? Anything wrong with my Delphi install? Also tried the same with an empty-form-app and using Embarcadero's default app icons. Same thing: icon is not showing within Application Loader... I was sooo glad seeing that there's finally 64bit support for Mac... Please help! Thanks!

Good news. Our app is now available on the Mac Store and Apple finally approved the MacOS app. Long story short, for whomever runs into the same issue and has the same question... Just continue while not seeing an icon and submit the app. Tell to have Apple review the app and after that process the icon magically appears from then on, also inside Application Loader. Thus, the icns file was perfectly fine. Somehow this is/was at Apple's end, and in the end, nothing to worry about. Hope this helps!

Thanks Scott. I think I'm close to the solution and currently waiting for Apple's approval to release the app. Once I'm 100% certain I will update this threat. As for adding a space to the app-name, unfortunately I had to do that manually, although it's quite easy to do: * first compile the app for MacOS (release-version). The result will be for instance "Filename.app", created in your scratch-directory * then rename that file into a file with the space in its name; for instance: "File Name.app" * then open Terminal and copy a script that says something like (make sure you change YOUR NAME into the name as you have mentioned it in your keychain): productbuild --component "File Name.app" /Applications --sign "3rd Party Mac Developer Installer: YOUR NAME" --product "File Name.app/Contents/Info.plist" "File Name.pkg" The output will be: "File Name.pkg" that you can submit to Apple's Store.

Did some more digging. I don't think Application Loader is the problem. * When I upload an ipa-package (for iOS) then the logo is shown inside the Application Loader. * When I upload a pkg-package (for MacOS) then no logo is shown. (see picture) As said in my original post, if I proceed to send the pkg-package to Apple no icon is shown inside App Store connect which probably means that the pkg truly does not contain an icon. Do you have the same issue or am I the only one with this? Do you know who to contact (or where to send this) to report this issue and find someone to help me?