Alright, I'm trying to upload my first app to the App Store, at first it got rejected due to a simple bug, But I can't figure out how to re upload the fixed version to iTunes Connect. When I try to send it through Xcode ou Application Loader, I get the following error:
The bundle uses a bundle name or display name that is already taken.
The app's version is 1.0, the build number is 1. I can't figure out how to replace the older rejected compilation with the new one. Every time I try sending a new compilation, I get this error. I already tried changing the app's version and bundle numbers. I also can't make a new version or even delete the app from iTunes Connect.
I'm using Xcode 9.
I probably rejected the rejected build, so the app's status is "ready to send" again, like in the beginning.
The error you have mentioned, does not seem to be about the version, but rather the app name. Its been asked and answered already
For versioning :
Read the Technical note on Version Numbers and Build Numbers.
Specifically :
For every new build you submit, you will need to invent a new build
number whose value is greater than the last build number you used (for
that same version).
You you will have to bump your build number.
Turns out it was the app's name (Display name)! Looks like that if you compile it with a different display name than what's on iTunes Connect, it will get you that error!
Related
I develop the app on a windows PC and then I send the file I'm using to a Mac from the company. From there I did an upload to the AppStore last week (after some problems) with a first Mac. I made some changes on the App and now I tried to upload again from another Mac. This time I am able to do the whole process without any mistakes but after clicking Distribute App and accepting everything and no Issues on XCode I get an email saying "The build status of MyApp (version) has changed to Invalid Binary". Inside the message they say the bundle id is already taken. I've checked this and on the details (Archive window) of my app I've got the correct identifier, same as in developer page from apple, and the team is also the same.
Of course all this is with automatic signing. And certificate is for distribution (I don't really know how to confirm, but this one is available)
I've got a couple questions about this.
Do builds have to be the immediate following? I mean, I can't jump from 1 to 4, for example?
I deduce version and build is always taken from the runner configuration on XCode.
Should I always submit the same folder? Instead of making new copies of the version.
On a desperate attemp of trying things I created a new version from App Store Connect plus sign in my App.
Can I delete it? Can I use the same version I named it on XCode to upload? Can I use any other named version to upload?
What else should I try? Next thing I'd do would be deleting the Bundle ID and creating a new one, but that doesn't solve my problems on the long term.
I am using:
XCode 13.2.1
macOS Monterey 12.2.1
I tried changing versions and builds on Xcode, expecting to create the correct one.
I tried from an old mac to see if it was that I haven't got the good certificates, expecting a correct upload.
We tried to submit a new build to iTunesConnect for updating an existing application. It is a quick patch for fixing one server url.
We changed two files: REST.plist for updating one server url and app_info.plist for updating the bundleShoreVersion String from 4.0.0 to 4.0.1 and BundleVersion from 4000000 to 4000001.
The 4.0.0 version was submitted three weeks ago without any issue.
However, we got rejected with Invalid Binary with 4.0.1 version and following email was sent to us:
Dear developer,
We have discovered one or more issues with your recent delivery for
"xxxxx". To process your delivery, the following issues must be
corrected:
The bundle uses a bundle name or display name associated with an Apple
app.
Once these issues have been corrected, go to the Version Details page
and click "Ready to Upload Binary." Continue through the submission
process until the app status is "Waiting for Upload." You can then
deliver the corrected binary.
Regards,
The App Store team
Any help will be truly appreciated.
This is explained right here:
The bundle uses a bundle name or display name associated with an Apple app.
This is likely a new automated check, and that's why your previous versions went through with no problems before.
It's saying that your app is using a display name (the name below the icon on the homescreen) that an app made by Apple uses - for example, if the label said "Mail", then you could expect it to be rejected for this reason.
Change your app name to something Apple doesn't use in their apps.
To resolve this issue, note that the values for both of these fields must be unique in your Info.plist file:
Bundle display name (CFBundleDisplayName)
displayed below icon on home screen
Bundle name (CFBundleName)
defaults to PRODUCT_NAME, used internally, e.g. in filename like MyApp.app
That is, your CFBundleDisplayName can be as unique as you want, but if your CFBundleName isn't, your upload will continue to fail.
Don't use the name like fitness its most common name try with different one. It's saying that your app is using a display name
you can resolve this issue by
1: Changing the app display name
OR
2: Change Target and scheme name.
My problem was related to the app name that was the same as a app native system.
Ex .: Safari
Change the name and build again
I want to update my app. I have a new version of the app and now it says "Prepare for Submission".
Now I want to perform "Prepare for Upload" but I cannot find this in the new iTunes Connect.
I have tried to upload the app to iTunes using Application Loader and Xcode 5.1 but still the status hasn’t changed and when I click on "Submit For Review" I get the following error:
You must choose a build.
It is quite weird but let me show what I have learnt from this new iTunnesConnect layout.
Step 1: You should wait around 10 min to 20 min to see your uploaded binary file in the prerelease section. .
Step 2: After you wait a while (10-20 min) then you would see the below icon
Step 3: Then you could able to see that your binary is ready.
Step 4: Then click on plus (+) sign, you now could able to choose your binary and then click submit for review button to finalize.
Look for it here:
Here's the new binary I uploaded:
Then, don't forget to create a new version and then assign the new binary to it (after process is completed):
I had the same problem, and waited for more than 8 hours without any result. The plus-icon never showed up under the build section!
Then I saw a new (tax-agreement) contract that I had not signed. I signed it, waited for a few more minutes, and then the plus-icon showed up!
The reason could also be that you are still releasing binary with the old TestFlight SDK in it.
A few months ago TestFlight updated their service meaning that it is now included in iTunesConnect, previously a TestFlightSDK was included in the project and various codes needed to enable TestFlight for users. This is all now depreciated. This means if you release a new version of an app which still has the TestFlightSDK included your binary won't appear in iTunes Connect and you will receive an email like this:
We have discovered one or more issues with your recent delivery for "blahApp". To process your delivery, the following issues must be corrected:
TestFlight SDK - TestFlight no longer requires an SDK to enable beta testing, crash reporting and analytics. To continue using TestFlight, set up Beta Testing in iTunes Connect and remove references to the SDK from the following executables: blahApp.app/blahApp
Once these issues have been corrected, you can then redeliver the corrected binary.
You need to remove the TestFlightSDK and also all code linked to the old TestFlight. Once this is done the binary should start being picked up by iTunes Connect as the answer above states.
The tricky thing about this issue is that if you're like me the email could go through to your junk, to an old account or if you're working for a client and don't have access to their personal email it is tough to find. Apple give you no other indication that this is what's wrong.
Hope this helps people with this problem going forward
Just took 19 minutes. If you click the activity tab you can see that the upload is processing.
At this time of writing, binary submission should take only few minutes to appear in iTunesConnect. When my binary did not show up for hours, I can immediately tell that something is not right. Most of the answers I found resolved to waiting. This was not the case for me. I went to ask Apple support and I got the answer. My app was missing purpose string for one of my protected data class (for iOS 10 and later). Once I provided the usage description and resubmitted it, the binary shows up right away.
I thought someone else might be facing the same problem. For a complete list of protected data class that requires descriptions, check out this link: https://developer.apple.com/library/content/qa/qa1937/_index.html
We tried to submit a new build to iTunesConnect for updating an existing application. It is a quick patch for fixing one server url.
We changed two files: REST.plist for updating one server url and app_info.plist for updating the bundleShoreVersion String from 4.0.0 to 4.0.1 and BundleVersion from 4000000 to 4000001.
The 4.0.0 version was submitted three weeks ago without any issue.
However, we got rejected with Invalid Binary with 4.0.1 version and following email was sent to us:
Dear developer,
We have discovered one or more issues with your recent delivery for
"xxxxx". To process your delivery, the following issues must be
corrected:
The bundle uses a bundle name or display name associated with an Apple
app.
Once these issues have been corrected, go to the Version Details page
and click "Ready to Upload Binary." Continue through the submission
process until the app status is "Waiting for Upload." You can then
deliver the corrected binary.
Regards,
The App Store team
Any help will be truly appreciated.
This is explained right here:
The bundle uses a bundle name or display name associated with an Apple app.
This is likely a new automated check, and that's why your previous versions went through with no problems before.
It's saying that your app is using a display name (the name below the icon on the homescreen) that an app made by Apple uses - for example, if the label said "Mail", then you could expect it to be rejected for this reason.
Change your app name to something Apple doesn't use in their apps.
To resolve this issue, note that the values for both of these fields must be unique in your Info.plist file:
Bundle display name (CFBundleDisplayName)
displayed below icon on home screen
Bundle name (CFBundleName)
defaults to PRODUCT_NAME, used internally, e.g. in filename like MyApp.app
That is, your CFBundleDisplayName can be as unique as you want, but if your CFBundleName isn't, your upload will continue to fail.
Don't use the name like fitness its most common name try with different one. It's saying that your app is using a display name
you can resolve this issue by
1: Changing the app display name
OR
2: Change Target and scheme name.
My problem was related to the app name that was the same as a app native system.
Ex .: Safari
Change the name and build again
Each time I attempt to publish an update to an app I receive this automated email response moments later:
We have discovered one or more issues with your recent delivery for "App Name".
Your delivery was successful, but you may wish to correct the following issues in your next delivery:
Version Mismatch - Neither CFBundleVersion ['9.1'] nor CFBundleShortVersionString ['9.1'] in the Info.plist match the version of the app set in iTunes Connect ['2.41'].
I understand why the message is being generated but I would like to resolve the issue without having to compromise the version # by making it higher than it actually is.
Being the first app I had ever developed, I was pretty clueless when it came time to publish the app and in frustration of the process I mistakenly defined the version number to some extreme value because I was, at the time, getting stuck with another error that was preventing me from completely the process .. the other error which I've since forgotten exactly, was related to the version number being incorrect. So I finally thru my hands in the air, set the version number to 8 and was able to complete the process.
Since then, I'm still pretty clueless but I've learned a thing or two, and the current version of the app is 2.41. When I prepare an update on iTunes Connect I set the version to 2.41. But if I define 2.41 in CFBundleVersion or CFBundleShortVersionString, Xcode outright refuses to upload the binary and demands a version greater than the previous version which has now surmounted to 9.1.
Obviously, any users of the app would be quite confused if the version jumped from 2.41 to 9.1 overnight.
It was you who defined the new version as 2.41 in iTunes connect. Any new version should be higher than the last one. So the straightforward solution is removing the 2.41 version from iTunes Connect and add a new 9.1 version. Then iTunes Connect and your binary will be in accordance and you will be able to upload the new version.