I just attempted to submit an app for review and get the following error:
New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK. Don't submit apps built with beta software including beta OS X builds.
I'm building with Xcode 7.2 (7C68) on OS X 10.11.3 (15D21), which was released this morning. Is anyone else getting this error when trying to submit?
Assuming you also didn't use a beta iOS, it sounds like the backend hasn't caught up w/10.11.3 just yet - give it another day or two.
I'm getting this as well, and I'm running 10.11.3. No beta versions of anything.
The last time this happened they had to update the back end of iTunes Connect to cope with the new version of OSX. I'll try again in a few hours.
I'm also getting this - running OS X 10.11.3 (15D21), still happening this morning. - I've seen this before with iTunes Connect not being out of sync with the latest XCode version, or in this case OSX.
I found the same problem with spudnik187after i updated osx El Captain version 10.11.3 this morning(jan 20, 2016) i'm using Xcode version Version 7.2 (7C68)
This is error message from ituneconnect "New apps and app updates must be built with the public (GM) versions of Xcode 6 or later, OS X, and iOS SDK. Don't submit apps built with beta software including beta OS X builds."
Just thought I'll also rise my hand and say I update to 10.11.3 and I get the same error. No beta software anyware. But it's good to know I'm not the only one 🙂
Hope this gets fixed fast.
Got the same error today with 10.11.3
I have the same issue with the same non-beta versions.
Yes, exactly the same happened to me now.
Should one just wait (for iTunesConnect no-more-warning) or should one upload new build in few days?
Same problem here.
Have the same problem. It's awful.
Same problem here. I'm not using any beta software, so as they mention above, probably a 10.11.3 issue.
Eactly the same issue. Looks like it's 10.11.3 issue indeed.
The issue is on the backend, where checks made during upload haven't been updated to appropriately bless 10.11.3. A classic left/right hand lack of communication priority fail, to be sure. Devs can expect things to right themselves just as soon as the winter intern-in-charge of such things comes back from their fieldtrip to the local firehouse.
I'm going to try and re-build with a machine I have that's running 10.11.2. I'll report back.
Scratch that. The keychain on my other machine is f*cked and I can't sign the build. I guess I have to wait...
