I have a (I guess) simple question: Where do I change the build number in iTunes Connect / Xcode to make sure they are consistent.
I tried to upload an archive and got the error that the app was uploaded but the build number was different from the one in iTunes connect. And I am wondering where I entered the number. Apparently I entered Build 1 although in Xcode I was working on build 20something. So where do I change this because I cannot go back to build 1 in Xcode, than I get an error while uploading that the build is smaller than the previous transmitted.
I should add that this is the first time I upload an app and I am happy that got to this point :)
Thanks
The version number in Xcode and the version number on iTunesConnect should be same. As shown in below images.
Whenever you upload new build for same version just increment build number. If you want to upload new version then you need to change version number as well as build number in Xcode. But this version number should match with version number on iTunesConnect.
Related
I have some problems with uploading dSYMs to crashlytics using Xcode 14. I saw a lot of similar questions and discussion on apple forum, but none if them are the same as my case.
Since in Xcode 14 bitcode is deprecated we can't download dSYMs from TestFlight. As i understand as long as flag "enable_bitcode" is set to no, dSYMs from my local archive (which was used to upload app to TestFlight) should be valid for crashlytics, but unfortunately there is a mismatch in dSYM uuid.
So in Firebase Console there is an information that for version X build Y there are missing dSYMs with UUID idX1 and idX2, but unfortunately when i check archive that was uploaded to Testflight there is no dSYMs with uuids idX1 or idX2.
Do i miss sth? I will appreciate any help.
When bitcode is disabled, these are usually the steps to follow:
Make sure that Xcode is generating dSYMs.
Follow these configuration steps to automatically upload dSYMs when building the app.
Increase the version/build number (this is to easily distinguish the new tests).
Do a small code change. This will trigger Xcode to generate a new UUID and related dSYMs.
Build the app and cause a test crash following these steps.
If everything went well, the correct dSYMs should be uploaded to Crashlytics. But, if you see "missing dSYMs" for the this version/build number, it would be interesting to see if something went wrong when uploading the dSMYs.
Typically, the run script will do some validations but will do the upload asynchronously. To override this behavior and do it as part of the build process you can use this other run script:
"${BUILD_DIR%/Build/*}/SourcePackages/checkouts/firebase-ios-sdk/Crashlytics/upload-symbols" --build-phase --debug
The --build-phase flag will indicate the script to upload the dSYMs during build time, this will make the build to take a bit longer but will give you the opportunity to obtain more information about this process. Also, the --debug flag will make the script to provide verbose output.
Things to look in these debug logs:
The UUIDs of the dSYMs files.
The App Id. Make sure this is the correct one. In some scenarios there can be multiple GoogleServices-Info.plist files and the script could be using the wrong file.
Errors in the upload process.
I archived the app I made, but then later made some changes. I'd like to replace the archived app with this new version. When I go to archive it, it gives me an error that says version 1 already exists. How do I get rid of the old one and replace it with the new one? I have not submitted anything for reviews yet. Thank you!
I'm not sure about the error that you see but try to change the build number:
It is related to build number error. Keep the version number same and change the build number by increasing one. And Now try to upload a new archive and itunes will accept this.
For example, You have uploaded last archive with version 1.0 and build number 1.0. Now, if you want to upload a new archive for the same version i.e. 1.0, then simply change the build number 1.1 and that's it.
I try to upload my Mac App to the App Store, but I am in trouble with iTunesConnect since one week by now. I definitely need your kind help.
I read the Apple documentation a couple of times and asked google for a solution. I tried new Certificates and provision Profiles, a lot of build settings and - yes - I even moved to a new mac with a fresh Xcode on it. No success so far.
Here is my story: I build and run my app successfully. I subscribed to the Mac Developer Program and configured my project to sign the application for a App Store submission.
I made an archive and validated it successfully.
Then I exported the Binary like the documentation suggested and all tests passed.
Then I uploaded the archive to iTunesConnect. The archive got processed and then... I got the little triangle near the build and as I clicked onto that build, there is absolutely no information all.
Sorry I moved to a german Mac and didn't change the language to English by now
After nine builds and one week of reading and trying I have absolutely no idea how to solve that problem.
Thank you very much for every new thought.
* UPDATE *
I removed the provision profile and created a new one. Then I built a complete new Project with the same ID and uploaded it as a new build number. Again, the pre-release tab is empty.
These are my code signing settings:
I uploaded a binary update to the new iTunesConnect, but had not submitted. I found a bug, and tried to remove the existing binary - could not find a way to do that. I then submitted for review but immediately rejected it. Still can't see a way to delete it and upload a new one. How do I upload my new version? OR how do I cancel my update and start a new one?
You don't need to reject Binaries anymore, just change the BUILD number to something higher 1.1 or something like that. Leave the version number the same.
Then it will let you upload it and you can select it from the list to add to your submission.
It took me a while to figure out but it's actually a much better solution than all the rejecting nonsense.
You can't delete binaries that are uploaded. I had to developer reject couple of times and I had 6 of these binaries there. I selected one and then submittted for approval. There is no way to remove "non-needed" ones from this list
One of the apps I've developed is submitted and approved to the appstore.
Because of some big changes and a more generic code I created a new XCode project for this app.
The problem is when trying to install the same app (based on bundle identifier) from the new XCode project, it quits with a crash. If I try to install again (Build & Run/Debug) from XCode, it seems to successfully overwrite and run. So it seems the first time there are some merge / overwrite conflicts. A second install, over the failed first attempt makes it work.
I wouldn't want this to happen with app updates downloaded from the store.
I've read that the idea is not to build from XCode, but use an Ad Hoc Build through iTunes instead. This would simulate a more natural end-user process. I've tried this, but somehow it won't sync / overwrite the existing app from the appstore (no errors, the app is just not changing).
Does someone have a hint on how to solve this?
Any help on this matter would be greatly appreciated!
I run into this problem all the time. I use one Developer Profile for all my dev work (and thus, one bundle identifier).
You have to delete the old App from the phone, and do a Clean Build.
These are similar problems. (1) (2)
As it seems working with an Ad Hoc build through iTunes does work.
Yesterday I double-clicked, but never got the iTunes message warning me of an older version existing in my apps and whether I want to replace it.
Dragging the .IPA into the iTunes app section did give me this message. Telling it to replace and next syncing works okay. iTunes sync status bar displays the message "YourAppName Updating". Afterwards launching it works fine with stored data intact.
The flow described here worked for me:
How to test an iPhone application update