1
0 Comments

Why I Got Rejected from Open Testing (and It Was Totally My Fault)

I just had a rough lesson in patience and timing while trying to publish my app on Google Play. I had applied for open testing and was in the review process. While waiting, I decided to clean up and update my website—specifically to polish the landing page and improve my privacy policy presentation.

Unfortunately, in the middle of that, I pushed a bad update that completely broke my site—it was down hard. And wouldn’t you know it, during that short window while the site was down, Google reviewed my app… and rejected it because they couldn’t access the privacy policy URL.

So now I’m stuck. The site is back up and working, but I have to wait to reapply, and I’m not sure if this rejection is going to count against me in any way going forward.

Lesson learned: Don’t get impatient and try to do everything at once. Wait for one thing to clear before making sweeping changes—especially to something as critical as your public-facing site. I thought I was being productive during the review wait, but I ended up hurting my chances instead.

If anyone’s been through something similar, I’d love to hear how the re-review went or if the initial rejection caused any long-term issues.

posted toAvatar for product PitchGrid
PitchGrid