I am compiling macos app with qt6.3, using QtCreator. My development system is xcode13, macos 12.3. I have set QMAKE_MACOSX_DEPLOYMENT_TARGET=10.15 in .pro file. I want my app to run on macos10.15. However, when I copied the app to the 10.15 system, the icon showed a forbidden match and prompted that the app requires macOS 11.0 at least. I checked everywhere and I never have the 11.0 version set. This is a very simple program, generated by QtCreateor.
I checked the qt6.3 documentation, the minimum support is 10.14
I checked the plist file in the app, the minimum version is 10.15, no problem, but it just doesn't work！
I've tried generating a simple program test with xcode,It's no problems.
How can I make qtCreateor generate a macos10.15 app?
Related
I recompiled my completed app so that it will run on OS 10.9, however when I try to open it in OSX 10.14.6 (Mojave), I get the contradictory panel warning: "You have macOS 10.9. The application requires macOS 10.14 or later." I double-checked the app's info plist file and it shows the target to be 10.9 as it should. What gives here?
I came up with a work-around. I upgraded my OS to Catalina 10.15.7 so that a downloaded copy of XCode 8.15 would run. Within this framework I was able to generate my app targeted for OS 10.9 that was kosher for Catalina. I suppose that the self-contradictory warnings when I tried to copy my older app onto OS Mojave had something to do with the lack of a code-signature, for I am still in the development phase of production and do not have a mac developer signature yet. However since this is not a full solution to my question, I am withholding bonus points from being awarded to myself.
In my Macbook, i have Xcode 11.7 installed and somehow my iPhone OS updated to iOS-14.
Then i couldn't build and run my project to the iPhone as Xcode-11.7 doesn't have device support for iOS-14.
Scenario 01:
I downloaded Xcode-12 and copied the iOS-14 device support file to Xcode-11.7.
When i build the project by Xcode-11.7 for iPhone-iOS14. It's only install the app to my iPhone by showing an error pop up
but there are no log showing in the xcode console.
Then i found the Xcode-12 release note
Xcode 12 now encrypts the connection between Xcode and paired devices, protecting against an attacker in a privileged network position executing arbitrary code on connected iOS, iPadOS, watchOS, or tvOS devices during a remote debug session. (60386733) These security benefits are available when Xcode 12 connects to devices running iOS 14, iPadOS 14, watchOS 7, tvOS 14, or later versions. These OS versions also refuse debugger connections from older Xcode releases. Xcode 12 continues to support debugging for older OS versions, but without the new encryption.
By this notes, it is clear that Xcode-11.7 or lower version should not be able to show debug log in the console from iPhone which OS is 14 or higher even though we use the hacky method to put device support file.
Scenario 02:
Some of my colleague are using Xcode-11.7 to build on iPhone-iOS14. They are not getting any issue what i'm getting in Scenario 01. The difference is that they downloaded the iOS-14 device support file from a github repo instead of coping from Xcode-12. Then i also tried to copy the iOS-14 device support file from that github repo & fortunately it also worked for me!
Now my question is
How is that possible to connect the debug session with iPhone-iOS14 using Xcode-11.7 where apple official release note pointed that it should not work?
The copy of iOS-14 device support file from Xcode-12 to Xcode-11.7 is not working but why its working when dowloaded from github repo?
I am developing an app for iOS and also using Mac Catalyst to run on my Mac. The app runs fine on my iPhone but always shows an error on Catalyst. The code used to run fine before updating to Big Sur Beta 6 from Beta 5. Here's a screenshot of the error: . Also the error in code blocks for anybody who wants to copy it.
The operation couldn’t be completed. (OSStatus error -10670.)
Domain: NSOSStatusErrorDomain
Code: -10670
User Info: {
"_LSFunction" = "_LSOpenStuffCallLocal";
"_LSLine" = 3664;
}
--
System Information
macOS Version 11.0 (Build 20A5364e)
Xcode 12.0 (17210.1)
https://github.com/MysteryCoder456/VegieMato/tree/backend is the GitHub Repo if anybody wants to reproduce this (i.
Faced same issue after upgrading to macOS 11 Beta 6. Reported bug to Apple but meanwhile found workaround - Select Product in Xcode, select 'Show in Finder'. Launch it from Finder. Additional step, hopefully Apple will look into it.
The problem is solved with new Mac OS 11.0 Beta (20A5374g).
If your catalyst app has multi-window support, you may still need to kill your existing app before launching the new one.
I also had the same problem. (I say had, I guess I still do, however I have a workaround) My App had been developed as iOS / iPadOS with Mac support. All has been working great throughout macOS 11 beta builds. Until today that is, when I, as you, updated to Beta 6. Upon attempting to run for macOS target I get the same error as you have posted.
After some googling I found https://www.virusbulletin.com/uploads/pdf/conference_slides/2015/Wardle-VB2015.pdf and had a go at simply opening the app directly from the build folder. Hey presto, it opened without any problems, I even cleaned out the build folder and built it again to make sure.
This would appear to be a problem that the next version of Xcode beta should fix. Until then, unless anybody can suggest a better fix, this will have to suffice for me at least :-(
Sam
-10670
I was having this same error code upon installing a Developer ID Distributed, Auto Signed version of a catalyst app on a test machine, non M1 Chip, Mac Mini(Late 2014) with MacOS Version 12.0 Beta installed.
The solution was to close the previously installed version of the app. Before opening the new version that I Airdrop over to the test Mac machine.
I'm having a bit of an issue with distributing an app via the latest version of Xcode (Version 10.1 (10B61)). Every time I try to upload it to the App Store via organizer, I get this error after uploading:
WARNING ITMS-90725: "SDK Version Issue. This app was built with the iOS 12.0 SDK. Starting March 2019, all iOS apps submitted to the App Store must be built with the iOS 12.1 SDK or later, included in Xcode 10.1 or later."
Previous answers to this question said that it was just a warning and that I should still be able to upload my app, but it is now March and I am still getting the error even on 10.1. iTunesConnect will not let me select these builds and I get emails about the validation failure.
Further details:
-The app is an iMessage extension, and uses exactly 1 framework from Carthage, which is up to date with the latest framework version and Carthage version.
-My project and Message extension targets Swift Language Version build setting is Swift 4.2.
-My deployment target is iOS 11.0, but the issue persists after selecting iOS 12.1.
-The app compiles and runs fine on my physical device running iOS 12.1.
-The issue persists after a build folder clean.
-The issue persists after reinstalling Xcode.
If anyone has any suggestions as to how I can verify my app is compiling with the latest SDK please let me know.
Whether the app runs on given iOS version, has no relevance to which SDK are you really using. The definitive SDK version used for building is found in the app's Info.plist.
after Archiving, Show the xcarchive in Finder.
right-click, Show Package Contents.
open Products/Applications/YourApp.app
right-click, Show Package Contents.
copy the Info.plist to some place where you can run terminal commands on it
/usr/libexec/PlistBuddy -c "print :DTSDKBuild" Info.plist
You would expect it to show "16B91" for SDK 12.1. If it's something else (SDK 12.0 would be "16A366"), here are some ideas:
inspect the Carthage dependency. Are you really building it locally or downloading a prebuilt binary? If in doubt, force local building with --no-use-binaries. Remove whole Carthage folder (Checkouts as well as Build) and start from scratch.
rm -rf ~/Library/Developer/Xcode/DerivedData instead of just "build folder clean"
Verify MacOS System Report section Software/Developer for the actual SDK versions that MacOS thinks that you have
xcode-select -p to verify that you are really using the Xcode instance that you would like to
If all looks correct on your side, fill Technical Support Incident. Report the exact rejected build which you uploaded already. That should speed up the support reaction.
I filled out a bug report with Apple because I was experiencing the exact same issue and none of the above solutions worked. They made a change on their backend and now everything is back to proper working order.
If you haven't tried in awhile, make another attempt and I'm betting that it'll work this time.
I was having the same problem. My app was compiled in Xcode 10.1 but I was still getting the SDK warning. I was able to resolve it by doing the following. I'm not sure if all these steps are necessary. I didn't try validating between steps.
I upgraded macOS to Mojave (10.14.3). I had been running High Sierra.
Delete Xcode from applications folder
Reinstall Xcode from the app store
Open my project and run Project->Clean Build folder
Archive and upload and no more warnings
I just updated to iPhone SDK 4 and am trying to debug on my device with 3.1.3 installed. Before the update, I compiled with Base and Active SDK set to 3.1.3 and all was well. After the update, I'm limited to SDKs 4.0 and 3.2--setting the base to 4.0 and iPhone OS Deployment Target to iPhone OS 3.1.3, I'm able to build and install on my 3.1.3 device, but receive the following error:
Error from Debugger: mi_cmd_stack_list_frames: Not enough frames in stack
I'm not using anything specific to the newer SDK, as I haven't touched a bit of code, just updated the SDK/XCode. So what am I doing incorrectly? The application runs as expected on an iOS4-installed device. Are there changes to pre-existing API's that need to be weakly linked perhaps? Thanks for all help.
Have you tried removing the app completely from your dev device, doing a build -> clean all targets, and then build again to your device?
I found this answer on macforums. If it's correct, then you probably have a memory corruption problem in your app that is confusing the debugger. Perhaps over-releasing something somewhere.
This probably isn't related to the SDK you are compiling with. It's possible you had this problem in your app all along but it just didn't show up until things moved around with the new Xcode, SDK, etc.
EDIT - I just ran into this problem myself trying to update an older app of mine to 4.0. It would run fine in the simulator and would install and run on the device except it wouldn't run in the debugger on the device. Anyway, I finally decided it was the .xcodeproj file that was corrupt or bad in some way and created a new project, copied over my source files to the new project and now it all works again. It's a pain but it only took about 20 mins to duplicate all my settings and I spent a couple hours trying to get the debugger to work.
Myself (and probably many others) are concerned about "will I still be able to compile/install apps for v3.1.3 of the iPhone OS?"
And what version of xCode does it become IMPOSSIBLE to ever write v3.1.3 apps again?
(Without installing a second copy of an older version of xCode.)
I've read the mile-long document that Apple wrote on the subject... but it sure would be simpler to understand if they just LISTED the various versions of each... instead of writing long paragraphs.
If you have:
Mac OS version 10.x.x x
xCode version x.x.x
SDK version(s) x.x.x
you can produce apps for iPhone OS x.x.x through x.x.x?