I wish to point out some inconsistencies if not blatant falsehoods....Originally Posted by Ceeg_LOT
Not true. You can supply Apple with an update and a FUTURE release date ensuring propagation has occurred BEFORE you make your update live. You COULD have supplied Apple with the update yesterday for a release of today, ensuring 24hr for propagation was allowed. The delay is ENTIRELY your fault for not taking into account how Apple works. They aren't rewriting procedures each month. You are simply ignoring their procedures.Originally Posted by Ceeg_LOT
Again, untrue. Each MONTH it typically takes an additional 4-6 hrs, above and beyond Android, for iOS to update. And in the past it has OFTEN taken 8+hours. Even taking as long as 23hrs one month. It has NEVER taken "an hour" not EVER.Originally Posted by Ceeg_LOT
I would believe that Nodding Frog may not WANT these delays if this was a first occurrence.. or even a second. But its not. These delays are NOTHING new and you COULD ensure they are minimized if not removed entirely. When an update occurs, iOS users are ALWAYS left wondering if they'll be locked out for 6 hours, 8 hours, 10 hours, 12 hours or more.... Your behavior makes it clear that you all just don't really care. And then you continually give the same lame "It's Apple's fault" excuse. I think we all know it's not Apple's fault. It's poor planning on your part that is to blame.
Apple doesn't care if your app is functioning... if you don't either.. well.....there ya go.. 12+ hr delays for users.
I have to honestly ask.. do you think your users are just stupid and believe this stuff when you post it, when ONLY your app has this problem???
--------------
FYI.. the app has just NOW appeared in the app store for me in the last 20 minutes or so.... (West coast US)