12 ms·

It's been a while but I think it was because it was considered a remote update mechanism. We planned to keep it limited to small layout fixes and such but in th

It's been a while but I think it was because it was considered a remote update mechanism. We planned to keep it limited to small layout fixes and such but in theory we could have changed everything about the app (it had news available in like 15 languages and there was always some new issue related to right-to-left, or CJK font stuff or etc. We didn't want to make all users have a new update just because Cyrillic needed some layout change or something). 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. In this case we decided to just remove that feature and re-publish.

joshstrange 3y ago
> 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.

joshstrange 3y ago

> 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.