Do you need a new build or just a console change?

You’ve hit an error or a review issue, and it’s tempting to make another build. First, check where the fix belongs. A reviewer password, an unanswered store form, and a missing feature need different changes. We’ll help you find the right place to start.

Copy the exact error and affected version. Note when it happens: before upload, during processing, in review, or after approval.

Where to make the change

What needs fixing	Where to start
Identity, membership, authority, or agreements	Developer account or Account Holder
Reviewer password, test data, or backend availability	Review access and backend configuration
Incorrect privacy answer or another editable declaration	The relevant store-console form
Missing permission explanation or behavior inside the app	App changes and a new build
Wrong signing, target SDK, or native dependency	Build configuration and a new build
Ready for Review or changes not sent	The final submission action
Approved version held for release	Publishing or release controls

Make the fix, then check its status

These examples show why the message alone doesn’t always identify the fix:

Message	Check before making another build
Reviewer can’t sign in	Test credentials, account roles, and verification steps; a missing review route can still need app work
First purchase wasn’t submitted	Inspect the submission’s purchase and group items
Invalid Data safety form	Compare declared and actual data flows; correct the form or the behavior causing the mismatch
Photo permission isn’t justified	Inspect the final Android bundle; removing a packaged permission requires a new build
Purpose string is unclear	Correct the explanation packaged in the Apple build
Deletion URL doesn’t work	Test the website and request handling; a working URL still needs a working deletion process

Read any resubmission instructions in the review message. Correct the part responsible and test the result.

For a metadata change, check whether the store allows that particular field or asset to change without a new version. One editable field doesn’t mean every asset works the same way. Save the correction and complete any required review submission.

For a new build, increment the appropriate build identifier and confirm that the store is reviewing that build. If the requirement concerns app behavior, you’ll need to implement it; a better description won’t satisfy it.

A save isn’t a resubmission

Reopen the submission or Publishing overview. Check that the reported problem is fixed in the app or console, and that the corrected item is in the review or release state you intended.

If the review message doesn’t make clear what needs changing, reply with a specific question about the affected item.