how to resubmit binary without reset the review queue - ios

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.

Related

App Store Connect: Can I un-publish a build that's been accepted?

I pushed build 4.1.14 to App Store Connect, and it got approved. It's in the Ready for Sale state. I realized there's a major problem with it, and don't want people to download it. Is there a way to un-publish it? To go back to the previous version (4.1.13) that I had before? Or to submit a patch or something that I don't have to wait a day to have approved?
No, the best choice you have is to submit an urgent fix build for expedited review.
Expedited reviews
You can request the review of your app to be expedited if you face extenuating circumstances, such as fixing a critical bug in your app or releasing your app to coincide with an event you’re directly associated with. Expedited reviews are granted on a limited basis and we cannot guarantee that every request will be expedited.
Critical bug fix. When submitting an expedited review to fix a critical bug, include the steps to reproduce the bug on the current version of your app on the App Store.
Next time, you can try the Phase Release in App Store. This type of release can be canceled.
BTW, the expedited review is a limited request. Don't abuse it.

Does Using TestFlight With Approved App Trigger New Approval

My app has been approved but is awaiting developer release as I want to release it manually. Before releasing, it however, I want to test using test flight
When I try to send the approved build to my testers, Apple asks for a login id and then gives me a dialog to Submit For Review. Is this just Apple being clumsy with their language or do they actually want to review it again before testing even though it's been approved?
Anyone have any experience with this?
Here is pic of dialog box
My experience is that the Store and TestFlight are two different worlds with two different approval processes — but that the former affects the latter in a peculiar way.
The way the issue you raise has arisen in particular for me is that you release, say, version 1.1 build 26 on the Store, it is ready for sale, and then you proceed with development and upload version 1.1 build 27 to TestFlight. Even though 1.1(26) is being sold already, and even if 1.1(26) was already released on TestFlight, 1.1(27) requires a new approval! In other words, it appears that an App Store release resets the approval clock, as it were, on TestFlight.
That is almost exactly your situation. The approval on the App Store apparently means that your next TestFlight upload needs a new approval. So yes, you will have to wait while it is approved. This usually takes just a couple of days.
Instead of using TestFlight, there is even more simpler method to test the Apple approved build (Pending Developer Release state) before releasing to Store. It is Promo code testing.
You can generate nearly 100 promo codes, if i am not wrong. These promo codes can be shared to the developers so that they can actually test the store build without releasing it to app store.
You can find many articles about Promo codes. I have shared one here.

iOS Build Resubmission in App Store

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.

iOS App rejected due to review team misunderstanding its use. Do i resubmit?

My app binary was rejected due to paragraph 2
2.2 - Apps that exhibit bugs will be rejected
The review team misunderstood how to use the app since it is location based. I explained more about how to test it and proposed another solution in the resolution center and i don't need to change anything in the binary.
Do i need to "Submit the app for review"? Or wait for the review team to respond first?
Edit: To be more specific what i am asking is: I send the extra info to the resolution center. Do i leave the submission as it is with app status rejected, or do i resend the same binary for review along with the info provided?
I would resubmit the same thing. Sometimes the reviewers don't take enough time to review. I've had a friend who has submitted the same exact thing twice. The First time it didn't go through, but with the second reviewer it did.

iOS - Do I need to re-submit in-app purchases after rejecting binary

Yesterday I set up 2 in-app purchases then uploaded the binary to go with them. Today I rejected the binary and immediately submitted another. Yesterday's in-app purchases are still showing as waiting for review.
I guess this means I don't need to redo and re-submit them as well?
If I understand correctly, you'll only need to resubmit in-app-purchases if they are moved to the "Developer Action Required" state. So as it stands right now, you should be fine.
Apple Support would be able to provide a much better answer though (anyone here would only be able to give you responses based on research and past experiences, which often are different from the present); you may want to shoot them an email.
"waiting for review" means they haven't even touched your binary yet. You're good.

Resources