I have an app approved by app store that is version 1.0, and I want to update the app to version 2.0. I changed version to 2.0 in iTunes. It's in the "waitin for upload" state. I have made some code modification in my version 1.0 and changed the bundle version as 2.0. When I am about to upload the appbinary using xcode, it still shows the version as 1.0. If I m to click the validate button, it gives a message that it's already uploaded. Should I change the bundle identifier? I'd be so grateful if you guys could help me out.
You should update the BundleVersion in your Info.plist file prior to compiling your final release build.
Is the iTunes state "Waiting for Upload"? If not, then you have not yet told itunesconnect that you are ready to upload binary.
Delete your build folder and/or check your target to make sure you are building your release target and not trying to send an old release build.
Related
A while back I was trying to submit an App using Xcode version 11.1 (11A1027) but I received an email from Apple with the following message:
ITMS-90424: Invalid Swift Support - The SwiftSupport folder is empty. Rebuild your app using the current public (GM) version of Xcode and resubmit it.
From what I know, 11A1027 is already a released version and so I am not very sure why there is a need to use the GM version of Xcode. Does anyone have any idea?
I tried some of the methods suggested in other posts but somehow could not resolve it.
Is this a bug in Xcode?
Solved for me in June 2020.
MacOS Catalina 10.15.5
Xcode Version 11.5 (11E608c)
Check that Command line tools(Xcode->Preferences->Locations) have this value
Configure PROJECT in project settings
Click to you project in Xcode.
Select project name
Set filter to Basic and Levels
Find Always Embed Swift Standard Libraries field (if not found - play with filters)
Set YES to this field for PROJECT(debug and release)
Configure TAGET in target settings
Click to you project in Xcode.
Select target name
Set filter to Basic and Levels
Find Always Embed Swift Standard Libraries field (if not found - play with filters)
Set YES to this field for PROJECT(debug and release) and set NO to this field for TARGET(debug and release)
see example
Clean project and create archive(Product->Archive)
In the dialog window right click to the created archive name -> Show in Finder
Right click to the archive name in Finder -> Show Package Contents
Delete SwiftSupport folder here
After that upload your build using AppStore Connect in Xcode with default settings.
I received this same email after uploading an .ipa file to App Store Connect through the Transporter app. The following is where I went wrong: I distributed the app using ad hoc.
The following steps are the solution for my error:
Archive app
Distribute on TestFlight and the App Store
Export
Open ExportOptions.plist in the newly created folder from the export.
Make sure the method property has the value app-store if you are uploading to App Store Connect/TestFlight like me.
Drag and drop the exported .ipa file to Transporter.
Deliver your app to upload it.
And that's it!
Original answer here: https://stackoverflow.com/a/62568526/10374366
I don’t think it’s a bug. But the best thing you can do is to just reinstall Xcode from the AppStore.
The solution here was in this "Invalid Swift Support - The SwiftSupport folder is missing" with Xcode 7.3.1. We needed to use the new -exportOptionsPlist flag with xcodebuild instead of the older -exportFormat and -exportWithOriginalSigningIdentity flags. The plist just needs to have the method key set to app-store.
Try upgrading to swift 5.0 and going to workspace settings, build system and set it to New Build System. This solved it for me in a React Native project using native iOS views. As far as I know swift 5 makes doesn't use the swift support folder any more.
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 developed iPhone app,
I successfully uploaded first version of my app in store few days before, then i made changes in my app and now i want to upload second version of my app, i made first version of app with Bundle version 1.0, and in my updated app i changed my Bundle version to 2.0.
finally when i try to validate my app from Xcode - organizer it shows me this error..
and here is screenshot of my appName-info.plist file
Please help, i am new to iOS..
In info plist add one more row "Bundle version". And set here 2.0
I have a version 1.0 on appstore.
I have just got version 1.1 approved for appstore.
When the app on version 1.0 is updated from appstore, there is a crash on the device. but when we download a fresh version of version 1.1, the app doesn't crash.
How can I test this using Xcode?
Please help.
Install your first version application to device through Xcode.
Then install your second version application to the same device through Xcode (Note: Don't delete the previous installed version from your device).
So it will not overwrite the app contends which will be available in your Library or Document Directory.
Then it will crash.. so you can get it the reason through Xcode console.
Maybe problem in your save files?
When in device with app 1.0 user will update to 1.1, then a folders Library/Caches, Library/Preferences, will stay.
When user is redownload a fresh 1.1 version, it seems this folder will be a empty.
For test him, try run 1.0 and after some operations in app, try to update to 1.1 over 1.0. If crash in app, XCode must catch him
I just tried to upload a completed app via iTunes Connect, and I received the following error:
The binary you uploaded was invalid. Apple is not currently accepting applications built with this version of the SDK.
I upgraded to the 4.0 SDK. I got this same exact error with the PREVIOUS version of the SDK as well. 3.?.? (whatever it was). Now in Xcode, I no longer have the option to select a previous version of the SDK.
Any suggestions?
you must download "Application Loader."
Make sure when you build the .app bundle for distribution, that you are building for "Device" and "Distribution" in the drop down menu of the main XCode screen.
Make sure in the "Project Settings" that you have set the base SDK to 4.0 and your deployment target SDK to 3.0 (or whatever you want it to be).. both settings are found in that "Build" menu. Settings are for the "Distribution" configuration
This will build the app with the latest SDK but allow users of 3.0 (or whatever you chose) to use the app so long as you only included API that was available in 3.0 or below.