So beta 1 expires July 24th and beta 2 was released on June 24th. Beta 2 expires on August 8th so will beta 3 be out July 8th (2 weeks after beta 2's release)?
So beta 1 expires July 24th and beta 2 was released on June 24th. Beta 2 expires on August 8th so will beta 3 be out July 8th (2 weeks after beta 2's release)?
So beta 1 expires July 24th and beta 2 was released on June 24th. Beta 2 expires on August 8th so will beta 3 be out July 8th (2 weeks after beta 2's release)?
There's a difference between a bug, and a critical/big/huge bug (the latter being the way it was presented in the thread). Right? Right.You people are truly amazing. I don't know why I even bother.
Yes, you can all hide your heads under the sand.
https://devforums.apple.com/thread/192676?tstart=0
At least 15 developers
https://devforums.apple.com/thread/192123?tstart=0
3800 views and 71 messages, and I won't count the number of developers affected
Thirdly, upon reporting this as a bug apple has designated it as serious bug and duplicated, meaning they have a lot more reports in this regard.
----------
Yes I can imagine millions of consumers would be extremely happy if this "no-bug" made it to the final iOS release.
But since it is NOT a bug theres no need to worry, anyone.
What I would like in Beta 3 is Quick Reply. Just my two cents on this thread.
I think they're saving this one for the public reveal in the Fall.
I agree, quick reply looks like it is coming. I can't phantom why the notification bar is so big. It is begging for some kind of actions. Mavericks has it already so its just a matter of time, surprise feature?
There's a difference between a bug, and a critical/big/huge bug (the latter being the way it was presented in the thread). Right? Right.
There is also a difference between a severity of an issue and essentially how widespread it is. There can certainly be very severe issues, but if they only apply in some very limited cases, and thus only affect a very small subset of users (and even only sometimes perhaps), those bugs overall might not create a necessity of a rush for a quick fix and a truly big deal made out of them.You don't consider a critical bug one in which a specific group of settings would cause the whole installation process to hang temporarily disabling the user's phone?
Granted, we are developers and can fix this issue by either installing fresh, reverting back to ios 6 or investigating further, but if this is not resolved then millions of customers could pottentially "brick" their phones when it comes to the GM.
Apparently resetting all settings prior to updating to seed 2 solves the problem for everyone affected. Consequently we can infer that there was a bug in the update process.
And yes, a bug that bricks the phone, even temporarily, is a critical bug.
One that is not critical is, for example, the status bar shadow issue.