4 ms·

These last few weeks was the first time I dealt with this process. App was rejected for reason 1, resubmitted, now there's a reason 2, which is they clearly did

These last few weeks was the first time I dealt with this process. App was rejected for reason 1, resubmitted, now there's a reason 2, which is they clearly didn't read the instructions how to continue, ok, resubmit with more instructions, and now rejected for reason 3. Resubmitted And finally passed. The reviewers were definitely not all applying the same rules/info. Released to prod and it had a major defect for 2/10 people. Dropped a minor update and it took ~48 hours for a review. REALLY frustrating.

pier25 5y ago
The first time I submitted an app it was rejected because something like "the screenshots must be taken from the app". The screenshots were taken from the simulator... It took a couple more days until the app was finally published while we had thousands of users waiting for it. The company I worked for provided services to schools and its students. Our call center was on fire for a couple of days with calls from annoyed teachers and parents and there was nothing we could do about it.
- hobofan 5y ago
  It's an unwritten rule (actually, I wouldn't be surprised if it's a written rule for their internal review process) that your app will be rejected on the first review. One of the most valueable insights a mobile freelancer working on our app gave us was to submit the app for first review at least two weeks before planned launch. Just as they anticipated, the first review came back negative because "hey, could you please also make the app work on the iPad?", even though we explicitly marked it as not available for iPad (and didn't include it in the app bundle) to cut down the scope for initial launch.
  - Aulig 5y ago
    I've managed to publish apps on the first try, but it's really rare. Most of the time I get 2 or 3 rejections and then an approval - just by continuously telling the app reviewers that the app does in fact comply with the guidelines, citing Apple's definitions of certain terms (which the app reviewers in many cases don't seem to know).
OldHand2018 5y ago
Fixing the major defect involved a minor update? You resubmitted it to Apple twice without noticing, and you're mad at Apple for all the "delays". Really? Other developers were waiting their turn in the review line while you were going back and forth with the reviewers on an update that was defective from the start. Take some responsibility!
- Volundr 5y ago
  You've never written a bug that wasn't discovered until production? I certainly have, and given that I still haven't found the secret to never doing so again, I also build systems that are updatable with as little friction as possible. I don't see how the parent failed to take responsibility. They were responsible for the bug. Apple was responsible for the delay in the fix.
  - tinus_hn 5y ago
    Were they? Apple does have a process for expedited review of critical bug fixes. But that’s not for ‘minor updates’. It’s not at all clear they attempted to get expedited review.
cwp 5y ago
I sympathize; this sort of thing is very frustrating. However, it's better than it was. I was working on iOS apps 7-8 years ago and it was just like the story above, but each review took 2-3 weeks.

pier25 5y ago

The first time I submitted an app it was rejected because something like "the screenshots must be taken from the app". The screenshots were taken from the simulator... It took a couple more days until the app was finally published while we had thousands of users waiting for it. The company I worked for provided services to schools and its students. Our call center was on fire for a couple of days with calls from annoyed teachers and parents and there was nothing we could do about it.

hobofan 5y ago
It's an unwritten rule (actually, I wouldn't be surprised if it's a written rule for their internal review process) that your app will be rejected on the first review. One of the most valueable insights a mobile freelancer working on our app gave us was to submit the app for first review at least two weeks before planned launch. Just as they anticipated, the first review came back negative because "hey, could you please also make the app work on the iPad?", even though we explicitly marked it as not available for iPad (and didn't include it in the app bundle) to cut down the scope for initial launch.
- Aulig 5y ago
  I've managed to publish apps on the first try, but it's really rare. Most of the time I get 2 or 3 rejections and then an approval - just by continuously telling the app reviewers that the app does in fact comply with the guidelines, citing Apple's definitions of certain terms (which the app reviewers in many cases don't seem to know).

OldHand2018 5y ago

Fixing the major defect involved a minor update? You resubmitted it to Apple twice without noticing, and you're mad at Apple for all the "delays". Really? Other developers were waiting their turn in the review line while you were going back and forth with the reviewers on an update that was defective from the start. Take some responsibility!

Volundr 5y ago
You've never written a bug that wasn't discovered until production? I certainly have, and given that I still haven't found the secret to never doing so again, I also build systems that are updatable with as little friction as possible. I don't see how the parent failed to take responsibility. They were responsible for the bug. Apple was responsible for the delay in the fix.
- tinus_hn 5y ago
  Were they? Apple does have a process for expedited review of critical bug fixes. But that’s not for ‘minor updates’. It’s not at all clear they attempted to get expedited review.

cwp 5y ago

I sympathize; this sort of thing is very frustrating. However, it's better than it was. I was working on iOS apps 7-8 years ago and it was just like the story above, but each review took 2-3 weeks.