To anyone who's managed to get their update through...

Discussion in 'iOS Programming' started by ayasin, Jul 17, 2008.

  1. ayasin macrumors 6502

    Jun 26, 2008
    How long is it taking Apple to process these? I'm getting concerned because I have bug fixes in the version I need to submit AFTER this one gets approved. I submitted Monday and still no word.
  2. admanimal macrumors 68040

    Apr 22, 2005
    I'm in the same boat, and I submitted my update on 7/9. Still in review.
  3. macintel4me macrumors 6502

    Jan 11, 2006
    Yep, same boat. I submitted updates to each of my three apps last Saturday, 7/12. Nada. I sent an email over to I received a reply yesterday from them saying I should contact instead.

    I'm sure what is happening is they are backlogged like crazy on apps in the App Store given the volume. Generally speaking, I would think Apple is making new apps a higher priority than updates.

    If you REALLY want to get your code out to the App Store in a matter of hours, you could simply submit it with a different name as a different app. Users may not like this though. :rolleyes:
  4. ayasin thread starter macrumors 6502

    Jun 26, 2008
    Ok now I'm getting pissed. I updated my app Monday night and still nothing. In the mean time my competition has managed to get TWO updates through the review process! WTF is going on Apple?!
  5. admanimal macrumors 68040

    Apr 22, 2005
    The only thing worse than it taking forever to get an update through is the fact there is pretty much no way to contact them to make sure everything is OK with it (i.e. that the update is at least somewhere in their queue).
  6. Dippo macrumors 65816


    Sep 27, 2003
    Charlotte, NC
    I looked at most of the productivity apps, but I only saw a few that were not at version 1.0.

    Also, you might want to put a link on your webpage to your app on itunes.
  7. ayasin thread starter macrumors 6502

    Jun 26, 2008
    Yeah I agree, but a few have been updated 2-3 times while I know that several have been waiting with no update.

    An oversight on my part, thanks for pointing it out. Corrected now.

Share This Page