Rejection: Guideline 1.5 - Safety

When I was preparing to submit a new application to App Store Connect, I received a rejection message that says the following.

The Support URL provided in App Store Connect, https://www.xxx.net/?p=8034, does not direct to a website with information users can use to ask questions and request support.

I immediately accessed the website at the said URL. And I saw a comment box after scrolling further down.

Shockingly, this is the 2nd time in a year for me to receive this same rejection. Just jump to a conclusion without scrolling further down, huh!? What a group of professional reviewers... I don't think this is a mistake. It must be part of a series of sabotage campaigns that started in March or April of this year.

The reviewer is looking for a page whose main purpose is support. A blog post with a comment box further down reads as content, not a support page, so it fails.

What reliably passes:

  • A dedicated URL (e.g. yoursite.com/support) used only for the app
  • The app name at the top so the reviewer knows they're in the right place
  • A visible contact method without scrolling: a support email address or a contact form (social links alone don't count)
  • Optionally a short FAQ
  • No login, no "coming soon", and it loads on mobile

I've published 20+ apps and hit this exact rejection more than once. I got tired of rebuilding the same privacy/support/deletion pages for every app, so I built AppLander.io to handle them.

Full disclosure, it's my product. But the checklist above is what actually fixes this, whatever you use.

The blog comment support approach was acceptable 15 years ago. It's still acceptable today. I don't remember whether or not I filed an appeal afterwords, but Rejection has been overturned. I'm not the one violating guidelines. The blame should go to the reviewer who cuts corners by relying on bots with no eyes.

I've published 20+ apps

This submission was probably my No. 400.