2

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.

Brandon Slaght
  • 1,025
  • 1
  • 12
  • 34

3 Answers3

5

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.

  1. after Archiving, Show the xcarchive in Finder.
  2. right-click, Show Package Contents.
  3. open Products/Applications/YourApp.app
  4. right-click, Show Package Contents.
  5. copy the Info.plist to some place where you can run terminal commands on it
  6. /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.

Pavel Zdenek
  • 7,146
  • 1
  • 23
  • 38
  • I appreciate all the details, and I tried everything all the way through. Unfortunately, nothing helped. The archive's info.plist has the current Xcode version, there is only 1 copy of Xcode on my computer, MacOS says Xcode is up to date, and forced carthage and derived data deletes both have not worked. Do you have any other suggestions? – Brandon Slaght Mar 23 '19 at 19:40
  • I do have a suggestion, kind of. Added at the end of the answer. – Pavel Zdenek Mar 24 '19 at 22:18
2

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.

Fallout
  • 21
  • 2
1

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.

  1. I upgraded macOS to Mojave (10.14.3). I had been running High Sierra.
  2. Delete Xcode from applications folder
  3. Reinstall Xcode from the app store
  4. Open my project and run Project->Clean Build folder
  5. Archive and upload and no more warnings
shim
  • 9,289
  • 12
  • 69
  • 108
jamesh
  • 74
  • 2
  • Appreciate the help but unfortunately this was one of the first things I tried. I even tried building on a different machine. – Brandon Slaght Mar 23 '19 at 19:42
  • Yeah, I was surprised this worked for me. I thought the ios update might have had something to do with it since I saw my app was linked with some system libraries. I didn't look into it too closely since this worked. A stretch but, maybe see if you have anything linked in /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS12.0.sdk. Or just delete/move that folder and see if it still compiles. Good luck. – jamesh Mar 25 '19 at 22:17