> But yeah it also probably was partly due to reviewer roulette. I've experienced the same on other apps, things that have been in the app for a year can suddenly get it rejected without a corresponding rules change from Apple. Just different interpretations of our code by a new reviewer.
Been there. The best is when I have an app that has actually been released on multiple other accounts (white label app) and then a reviewer wants to say it's all wrong and reject it. I the worst thing that's happened to me is when they dinged me for a soft permission prompt (asking the user before throwing the one-time-only system dialog), I removed it since I needed to get the update out (it wasn't related to this at all of course), then they started nit-picking and not only were they wrong in a lot of the cases but they were making me do like 1-2 word changes to permission prompts to make them more specific. I had no clue how many new things they'd come up with for each submission, we went back and forth a few times before it finally got through, I just bumped the build number and resubmitted.
Been there. The best is when I have an app that has actually been released on multiple other accounts (white label app) and then a reviewer wants to say it's all wrong and reject it. I the worst thing that's happened to me is when they dinged me for a soft permission prompt (asking the user before throwing the one-time-only system dialog), I removed it since I needed to get the update out (it wasn't related to this at all of course), then they started nit-picking and not only were they wrong in a lot of the cases but they were making me do like 1-2 word changes to permission prompts to make them more specific. I had no clue how many new things they'd come up with for each submission, we went back and forth a few times before it finally got through, I just bumped the build number and resubmitted.