I'm updating my existing app to include support for Apple Watch (at this stage just handling of notifications), however when I archive my app and try to submit it to the app store for review I continually get this error.
I've tried playing around with the build settings and I've also tried googling the error, however I can't figure out what the issue is.
Does anyone have any ideas or has anyone come across this issue too?
You cannot submit an app for review using a beta version of Xcode.
Following today's Apple Watch official release, Apple updated Xcode to version 6.2 which in theory should allow submitting apps that contain Watch extensions. However I just tried to submit my app that includes support for Watch using the new Xcode, and got the same error. I hope this will be fixed sometime soon on the ItunesConnect site.
Related
I am trying to make my first application to submit to the App Store using Xcode, but when I was going through validation, it said that I had the wrong SDK version. How can I fix this?
I tried archiving my app 19 more times, but it didn't work.
I tried looking all over the web, but it didn't help.
I also tried updating
the Xcode app, but it said that it was temporarily unavailable.
When I would try to validate it sent me an error message saying that I had the wrong SDK version.
I thought that I did everything correct, but when I was at the last bit of validating it, it said:
"SDK Version Issue. This app was built with the iOS 11.4 SDK. All iOS apps submitted to the App Store must be built with the iOS 11 SDK or later, included in Xcode 9 or later. Further, 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.
Click here to see the image of the error message.
I think what I need to do is just put my app in a certain file and update my Xcode, and validate it again because on the error message it said that I had the wrong version of Xcode. When I said that I got another error message on the App Store
Thanks to everyone who helped me in the comments above - #manishsharma93 -. :D :)
Trying to upload a binary, which includes a watch app. The error I'm getting (which I wasn't getting a couple days ago) is the value provided for LC_VERSION_MIN_IPHONEOS for the watchkit extension is 8.2 which is greater than the maximum allowed value of 10.3... apparently 8.2 > 10.3?
I'm updated to the latest XCode, 8.3, that didn't fix the problem. Tried changing the iOS deployment target for the watch app and extension, no apparent effect on the message.
Update: it's fixed!
I have submitted a bug to Apple. They have replied that they are aware of the problem and have people looking into it. They will contact me when they have resolved the issue. I'll post an update here when they do.
This is not related to Xcode 8.3, the error is in the Apple validation process. I had an app in review (no problems in uploading it) that got rejected because the user provided for login had expired. I made no changes to the app, just activated the user and submitted. I have the error now.
Edit: I can also confirm that if Watch support is removed everything goes well.
EDIT: This is problem on Apple side and nothing to do with Xcode. This is only effecting apps with WatchKit.
I just uploaded one my apps today that has a watchkit extension. Try this, it may or may not help.
Xcode -> Product Clean
Xcode -> Quit
In a console terminal do > rm -rf /Users/your_mac_user/library/Developer/Xcode/DerivedData/*
Relaunch Xcode and project
Go to your Xcode -> Build Settings for your iPhone app and make sure its set to 8.0 for debug and release
Now go to both your watch and watch extensions and make sure the Build setting is set to 8.2
Archive and upload again.
EDIT: Although successfully uploaded to iTunes Connect, when trying to submit a Testflight beta build, still got rejected by the same message
Invalid sdk value. The value provided for the sdk portion of
LC_VERSION_MIN_IPHONEOS in XXX.app/PlugIns/XXX WatchKit
Extension.appex/XXX WatchKit App.app/XXX WatchKit App is 8.2
which is greater than the maximum allowed value of 10.3.
Guess Apple's still working on it...
I am having this issue earlier, also with a watchOS1 target in my project.
I've tried to upload the binary again few minutes ago, no more warning shows, and passed the processing of iTunes Connect.
Everybody having this issue should give it a try!
I was submitting with an old Xcode version, I thought that was the problem, so went to the latest and it gives me the same message, that I am submitting for 8.2 which is higher than 10.3.
Now, here is where it gets really crazy. I said, OK, maybe there is an issue with 8.2, so I switched my minimum target to 8.3, cleaned, archived, submitted. I STILL GET THE MESSAGE ABOUT 8.2!!!
I exported the package I am uploading:
otool -l MyApp.app/MyApp |fgrep --after-context=3 LC_VERSION_MIN_IPHONEOS
cmd LC_VERSION_MIN_IPHONEOS
cmdsize 16
version 8.3
sdk 10.2
--
cmd LC_VERSION_MIN_IPHONEOS
cmdsize 16
version 8.3
sdk 10.2
I grepped both the package and my project directory, there is no friggin' "8.2" string anywhere. The same app without the watch extension validates fine. It seems they have broken the watch submissions (at least WatchOS1), which is something they should have noticed, yet I emailed support 2 days ago with screenshots and they were unimpressed, telling me to send them a video if I want my ticket to be processed! Take 1 minute to look at the upload log, I gave you app ID and timestamp, how hard is that?
Edit: It seems I installed the previous version of xcode, there is one newer out, but it also doesn't fix the issue, the problem appears to be on the Apple side...
Edit 2: The binary that has not been going through since the day before yesterday, just got uploaded. Maybe it is fixed?
Edit 3: But then you get the message in itunes connect when you try to submit the app. So it seems they are working on it, not completely resolved yet.
Edit 4: SUCCESS! Successfully submitted, waiting for review!
Apple fixed this bug yesterday. You can use the same binary. There's no need to make any changes.
I deleted the watch-related targets, and uploaded successfully.
If you download a new version of Xcode, make sure to switch to it:
sudo xcode-select --switch /Applications/Xcode_11.6.app/Contents/Developer
sudo xcodebuild -runFirstLaunch
Ecuador's answer about using otool is a great tip to make sure the SDK is correct before you submit.
I too had the same issue. Removed the watch app and did the upload. It has been accepted for review. So looks like the issue is with the validation of the watchkit extension. Will submit the app again with the watch app once this issue has been taken care of by Apple.
Had just done an Xcode 7.3.1 built iOS app update to the App Store a few weeks ago with no problems. Now that a new Xcode is out I always do a TestFlight rebuild of the same update to make sure no regressions were introduced by Apple.
Ran into an error today I've never seen and cannot find any info on with Xcode 8. The error is at the very end - on validating the archive prior to submission. Happens both when manually validating the app, or attempting to upload the app to Apple. Screenshot attached below.
Same project still builds/archives/validates fine using Xcode 7.3.1.
Anyone hit this Xcode 8 problem know what causes it?
run Product->Clean and try again
try to upload it with the Application Loader (Xcode->Open Developer Tools). This often gives you a more detailed error description.
So I found someone posted a similar question to mine with this same problem and it was answered there. I have up voted that answer as it works and am cross-linking it here for others Must use MinimumOSVersion in info.plist
Best action though is to delete this from the info.plist, this should not be added manually for an iOS app.
I downloaded Xcode 7.1 from the App Store today after working from 7.1 beta downloads from developer.apple.com and have a new iOS app build to upload. So I did:
Product > Archive
Upload to App Store (or Validate)
But the response was:
You are not authorised to use this service
Intriguingly, when I 'Export' the build to the Desktop and then use Application Loader 3, it uploads without error.
Is this an iTunes Connect bug? Or is there a new Xcode checkbox I've missed?
Note: I've also tried removing and re-adding my AppleID as suggested here, and restarted my Mac for good measure (which actually allowed the validation to work once), but still no luck uploading directly from Xcode > Organiser.
I met the same issue today and I think it is a bug of Xcode 7.1
Finally I managed to submit my app via Application Loader. There were warnings but it did work.
Here are the basic steps:
Archive
Export
Xcode menu --> Xcode --> Open Developer Tool -->
Application Loader
Double click "Deliver Your App" and choose the
file exported in step #2
click next and follow the instructions until
the end
Here's the quick solution:
Don't use Xcode beta versions to submit apps for release — it's beta for a reason and shouldn't be used with production code.
Submitting Apps
Apps that are created using beta versions of Xcode or that are built
for beta versions of operating systems will not be accepted on the App
Store and Mac App Store. Apps that you submit should be developed
using the latest version of Xcode from the Mac App Store and should be
built for publicly available versions of iOS, OS X, and watchOS —
except when GM seeds are available. When a GM Seed of Xcode becomes
available, use it to develop your app for submission. When GM seeds of
iOS, OS X, or watchOS become available, build your app for these
versions.
↳ https://developer.apple.com/support/pre-release-software/
Having the same problems as all of you, just thought I'd share that I found a way to Validate successfully, you have to disable the "Include bitcode" checkbox before moving forward. As for the actual upload to App Store, no work around for that one other than use the Application Loader...
Also I've been seeing this too since XCode 6.4, but it seems once the current version has a couple of months after it's originally released it starts working again... fingers crossed that it starts working again soon, because uploading straight from Organizer is so much better. (I saw the Beta Version post, when I say after a couple of months for current version I'm not talking about Beta versions, just in case ;) )
Same problem here.
Downloaded Xcode 7.1 from the App Store and it refuses to upload a new version.
Happily Application Loader worked ;)
Hopefully this gets fixed quickly.
One possible reason for the issue could be multiple development accounts under one name (personal and company). I've read elsewhere (apple radar) that that caused earlier problems of this kind.
Happens here if the dev account is only admin. I had to use the central account for uploading our apps. I think this problem startet sometime with XCode 6. Didnt investigate further though since Application Loader works in cases when I dont have access to the central account.
I also have the same problem today.
Finally, I used the application loader to upload successfully,too.
Theres a few solutions I have come across to solve this issue.
Most common being to remove and re-add your developer account.
This won't work on its own though, you need to also 'view details' on your account and have Xcode download your provisioning profiles again.
The other alternative is to upload your build using application loader. The disadvantage to using this solution is that should you be trying to upload using a beta build of Xcode or OSX you won't be able to change your apps .plist in the archive folder to trick iTunes connect into accepting it. In this instance all you have access to is your ipa.
Disable the "Include bitcode" checkbox worked for me.
I am trying to submit an app update for an iOS app to support devices running iOS 9, and in the process of uploading to the App Store via XCode, I'm getting the following error:
No version found for 'adamId - platform' (936823648-Mac OS X App). If this problem persists for more than 24 hours, please contact your Apple representative.
This is an iOS app, not an OS X App, so I don't know why I am getting this error. I have already submitted several versions of the app to the App Store previously.
Anyone know how to resolve this issue?
I solved the problem by submitting the app using Application Loader instead of uploading via XCode. Seems like it might be an issue with XCode 7?
https://itunesconnect.apple.com/apploader/ApplicationLoader_3.0.dmg
As #scientiffic says in his answer. You should use Application Loader to upload your app. I thought using ANY version of Application Loader would solve this problem but no.
You need Application Loader 3.0 version. It doesn't work if you use Application Loader 3.2.
I realize this is an old question, but I have had this problem for about a year with no resolution from Apple. I had been using an old version of Application Loader as a solution to this problem, like many others, until I ran into a complication (I have one Apple ID that is attached to multiple iTunes Connect accounts and older versions of Application Loader do not support this). Essentially, I had to find a solution that allows me to use newer versions of Application Loader/Xcode to submit binaries or I was dead in the water.
It turns out I had a key in my Info.plist that was Mac OS X specific. LSMinimumSystemVersion or “Minimum system version”. Removing that key from the Info.plist solved the adamid - platform error.
Just for the record - this error message also comes if you are trying to upload an app for a wrong platform - e.g. uploading an iOS app with a bundle id that is registered as a tvOS app on iTunes Connect.
You can use tvOS/iOS with identical app ids (for e.g. universal in-app purchases), but both platforms must be enabled manually on iTunes Connect, or you will get this cryptic error (at least true in XCode 8).
Saw this when the tvOS version did not exist on the App Store.
I fix that by adding a 1.0 version to tvOS APP as the screenshot.
Same problem with Application Loader 3.5.
Downloaded 3.0 as mentioned and it worked.
You might get this error if you haven't set up iTunes Correctly to accept an app upload. I.e. its possible you haven't created an app with the matching bundle id within iTunes Connect.