Support URL not functional rejection: Guideline 1.5 fix
What App Store Guideline 1.5 says
Guideline 1.5, Developer Information, states that people should know how to reach you with questions and support issues, and that your app and its support URL must include an easy way to contact you. The support URL is one of the metadata fields you set in App Store Connect, and a reviewer opens it to confirm a user could get help.
The bar is practical: the page has to load, and a user landing on it needs to find a way to contact you quickly. A link that does not resolve, or a page with no contact method, fails the rule. The official text lives on the App Store Review Guidelines page.
Why apps get rejected under 1.5
Common triggers:
- The support URL does not resolve, returns an error, or times out.
- The page is a coming-soon or placeholder page with no real content.
- The page exists but offers no contact method, only an FAQ or a marketing blurb.
- The field points at a bare social media handle that gives no direct way to get support.
- The domain expired or the path changed, so a link that once worked now breaks.
The thread is that a user with a problem could not actually reach the developer from the page Apple was given.
How to fix it
- Make the page resolve. Confirm the support URL loads in a browser with no error, on the exact address entered in App Store Connect.
- Add a real contact method. Put a support email, a contact form, a phone number, or a ticket system on the page, visible without hunting.
- Replace placeholders. Swap any coming-soon page for a real support page with current information.
- Use a stable address. Point the field at a domain and path you control and keep live, so the link does not break later.
- Update the field and reply. Correct the support URL in App Store Connect, following the guide to manage app information, then respond in the Resolution Center.
Remember that submitted is not approved. The corrected metadata goes back through review, and Apple opens the page again to confirm the contact method.
How AppFlight helps
AppFlight runs the submission flow and sets the App Store Connect metadata for your app, so the support URL is part of the path to the store rather than a field that is easy to forget. When Apple returns a 1.5 rejection, AppFlight reads the rejection reason, works on the metadata, and resubmits, and because the support URL is metadata the turnaround does not require a new build. AppFlight does not host your support page, so the address you provide still has to resolve and offer a real contact method. AppFlight does not guarantee approval. Apple reviews every app and every resubmission.
FAQ
Why was my app rejected for the support URL?
Under Guideline 1.5, the support URL in your metadata must resolve and give users an easy way to reach you. Apple rejects it when the link is broken, loads a placeholder or coming-soon page, or offers no real contact method.
Does fixing the support URL need a new build?
No. The support URL is metadata in App Store Connect, so you can correct it and reply in the Resolution Center without uploading a new binary. That makes this one of the faster rejections to clear.
What counts as a valid support URL?
A page that loads and lets a user contact you within a moment, such as a support email, a contact form, a phone number, or a ticket system. A bare social media handle or an FAQ with no contact method is often not enough.