My app was rejected for not providing valid test account credentials, however the reason these credentials dont work is a problem with the binary.
I resubmitted with what I believed was an updated binary and was rejected again but the problem I think is that the original binary is being used for review.
What is the correct process to update this binary? I incremented the build number and archived / uploaded.
Is there anyway to restart the submission process to be sure, the current status of the app in itunesconnect is iOS 1.0 Metadata Rejected
You can move the binary to Developer Rejected
Make sure that you update the version number as well, even if you haven't really changed anything
Related
I submit one build in App Store. They rejected the build due to some network issues. I checked again and again to reproduce the issue , but I could not. So I submitted the same binary again. They rejected again.
My question is :-
Should I take new binary if one is rejected (even if no change in binary) ??
Thank You
No
You don't have to reupload new binary if there is no change in code.
Contact Apple resolution center and submit an appeal.
You can find link to submit an appeal from App Review Guidelines
If your submission was "binary rejected" you can re-submit the same binary but is usefull. If you build was rejected for any reason and you don't change anything there's no reason because your binary the second time may be acepted. This is the theory.
So first of all try to investigate on the reason by contacting apple support as suggested by #Muhammad Adnan.
In my esperience my app was rejected because reviewer said that crashed two times. I've try to reproduce the issues with no luck. Finally I re-submit the binary increasing the built number and some minor change in the code:
The app was approved.
On this month, soon after new iTunes Connect was available, I added a new version of my app.
But right after submitting for review, the app was rejected due to invalid binary error.
So, I rejected(deleted) the binary myself and built the app again without modification but adding +1 to the built number.
And I uploaded the binary using Xcode 5 and submitted for review again.
And about 10 days later, it was approved.
But a problem happened.
The build number of the app I downloaded from the App Store was the build number which was rejected due to invalid binary.
I checked iTunes Connect now, but the selected binary is the 2nd binary which I uploaded after the app was rejected.
Fortunately, the 1st binary which was rejected but released unexpectedly is working properly.
But I'm now submitting another next version of the app.
And this time, I don't want the same issue to happen again.
Is the issue still happening now?
Did you experience the same issue in the new iTunes Connect when you rejected a binary and uploaded another binary like me?
I submitted another new version of an app after I posted the question.
And I rejected the binary of it once myself.
And this time, just in case, to avoid the same issue, I changed not only build number (CFBundleVersion) of the app but also the version number (CFBundleShortVersionString) of the app.
(The last time, I only changed the build number.)
And a week later, the new version was approved.
And the version number and build number was correct. This means the same issue did not happen.
I don't know that changing only build number (CFBundleVersion) causes the issue.
But I recommend that you change version number (CFBundleShortVersionString) as well as the build number (CFBundleVersion) when you re-upload your binary to the iTunes Connect.
I had read once that if in iTunes Connect you marked a binary as "hold for developer release", there was a way to install that version from the app store instead of the current version in the store - thus allowing for one final check that the binary was good before release, and to ensure which binary was actually submitted.
I was unable to find a way to link to the approved binary though in a recent submission. Does anyone know how you can install an app store binary that has been approved before you release it?
What I do is an archive build (a release build). Then in the Organizer I choose the archive and then distribute it as an ad-hoc build. The resulting ipa file gets installed into iTunes then that version gets synced to an iOS device for testing. If it all looks good I then go back to the Organizer and choose the same archive. This time I choose to do an App Store distribution and submit the app to Apple for review.
The only difference between what you end up testing and what ends up in the App Store is how the app is signed. It's the same binary otherwise.
I think I may have found the answer in the response to this question:
Submitting third version of an iOS app via iTunesConnect before app goes live
Basically the idea is you could set a future release date, and click the release button - the binary would not go out until that date, and theoretically then there would be some way in iTunes Connect to find a link to use to install the approved binary from Apple.
That is all hypothetical, the next time I have an application ready for release I will attempt that and adjust this answer (unless someone else provides a clear answer before me).
I'm facing some problems with uploading an iOS application to the Apple store. For the very first time, I uploaded and submitted my iOS application and it was rejected by the Apple team. They mentioned that they want authentication for my application, so I put authentication and uploaded my binary again. It was rejected a second time. This time they mentioned that I need to put authentication in my application. That's when I realized that my application is not getting updated.
The first time I made changes, I used the Organizer in Xcode to upload my binary (navigate to Organizer -> Archives. Then validate first and distribute).
The second time I made changes, I used the Organizer to upload my updated binary again.
However in all cases my binary is not being updated. How cam I fix this problem, it is a real headache for me.
Thanks.
You need to supply that authentication data within the iTunesConnect review information. There are specific fields named
Demo Account Information
and
Review Notes
Fill in that account information within that first field.
Try to check the archive date in Organizer before you submit binary to App Store. When ever you make any changes to app Archive it again to reflect changes on your binary. Otherwise your binary won't reflect changes you made on code.
Apps that are “beta”, “demo”, “trial”, or “test” versions will be rejected. If you use any word related to these in the content , name etc. will be rejected.
Secondly Pay special attention when you are using any social networking site information in your app. e.g suppose if you got many permissions from Facebook but you are not using that information in your app your app will reject. So be precise while using permissions from social networking sites.
Apple once rejected my app because i violated the iCloud deal of unpacking 2MB data from app bundle into the file system. So for downloading data more than 2MB should not create any backup. For this you can use non-user data, cache storage or mark it with “Do Not Backup”.
Hope that helps!!
Hi I have uploaded my app and it is waiting for review at the movement, i have found issues that i fixed after upload, now how can i reupload it without a reset? i can see reject binary button but that will trigger reset according to apple(Please note that if you reject a binary that is Waiting For Review or In Review, your review time will be reset and you will start over from the beginning once you submit a new binary. )
also how long does it take from waiting to review to review?
thanks
Apple specifically says that submitting a new binary always bumps you to the back of the queue, period. Otherwise people would try to game the system by submitting apps a week ahead of when they think they'll be done, and planning to swap in the final binary just in time.
If you found the issue, Apple likely will too, and they don't approve apps that crash during review. That'll bump you to the back of the line too, so might as well re-submit now.
It's been my experience that Apple usually gets to new submissions between a week and two, and minor updates are sometimes approved in a couple of days.
There is no way to upload a new binary without going to the end of the review queue, AFAIK or can find in any Apple documentation.