TestFlight: ERROR ITMS-90512: Invalid sdk value… 8.2 is higher than maximum allowed value of 10.3?

I have uploaded the iOS App to test flight and have received this email from itunes from xcode 8.0

Invalid sdk value - The value provided for the sdk portion of LC_VERSION_MIN_IPHONEOS in ABC.app/PlugIns/ABC WatchKit Extension.appex/ABC WatchKit App.app/ABC WatchKit App is 8.2 which is greater than the maximum allowed value of 10.3.


Have already validated App deployment version is set to iOS 8.0 while for watchkit Extension its 8.2, the same was working in last release, as there where have not been any changes, not sure what the issue.


Can it be due to iOS 10.3 been recently released some how its restricting any upload to test flight.

The same problem. Any ideas? The message itself sounds weird: "8.2 higher than 10.3"?


"ERROR ITMS-90512: "Invalid sdk value. The value provided for the sdk portion of LC_VERSION_MIN_IPHONEOS in XYZ.app/PlugIns/XYZ WatchKit Extension.appex/XYZ WatchKit App.app/XYZ WatchKit App is 8.2 which is greater than the maximum allowed value of 10.3."

I am having this problem as well. Happens with both Xcode 8.2.1 and 8.3. It does seem to be an iTune Connect validation problem.


I did get it to upload last night without the error, but it has never appeared in the "Processing" list or the list of builds I can submit for review. If I try to upload again I get the original error.

We have the same issue, building with both 8.1 and 8.2.1. We're currently working under the premise that this issue may not be fixed in a timely fashion, so we're looking to change our project configuration. My understanding is that the setting in question is for watchOS 1 apps. Is your app supporting watchOS 1, and if so, does it work if you remove that configuration?

Appreciate your input.

Same issue with me as well. It was working perfectly till last night, before updating XCode to latest version. Any solution?

Used to be that the store lagged knowing about a new Xcode - this time, we didn't see that happen, so my guess is that when they fixed the delay with Xcode proper, they didn't get all the upload checks right, and this is a misplaced flag on the backend. Wait a bit to see if they deal with it soon.

I changed the deployment target to watchOS 2.0 and still no luck.

I've also been having this problem since yesterday and nothing I've tried (using an older version of Xcode, etc) has solved it.

same issue when upload a release version

I delete the watch related targets, and upload successfully

Yep thats the only way we are going with.

We have the same issue.

Deployment Target of the App: 9.0

Deployment Target of WatchKit Extension and WatchApp: 8.2


Everything worked fine in the previous release some days ago!


We build with Xcode 8.2.1.

Exactly the same issue here with XCode 10.3, iOS 8 as deployment target and WatchOS 1.0 compatibility. Removing the WatchKit targets is not really the way to go for us.

Same issue with me too. Removing the WatchKit targets is not a good way

What is the right way to get Apple's attention to this issue? Do they read this forum?

I informed them by using one of my Tech Incident tickets. Seemed the most direct approach to me, but no response yet.

TestFlight: ERROR ITMS-90512: Invalid sdk value… 8.2 is higher than maximum allowed value of 10.3?
 
 
Q