Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Work Continues on iOS 8.1.3 With Retail Employees Receiving Second Beta Seed
- Thread starter MacRumors
- Start date
- Sort by reaction score
I asked a similar question a few weeks ago.
No, people aren't correcting the same bugs again and again, they're more organised than that.
iOS 8.2 exists chiefly because of WatchKit. I imagine 8.2 right now is 8.1 + WatchKit. When it's finally released, it will be 8.1.3 + WatchKit.
For more accurate info: http://en.wikipedia.org/wiki/Revision_control
Last edited:
Depending on how this turns out fixing long standing issues, this may be my last dance with the iPhone. I pay too much money to have a phone with these kinds of bugs. If I was on a cheap Android phone, I would understand, but not for $850 device.
How can this be the "most advanced mobile OS" when the screen rotation doesn't work consistently, the music app skips as I switch between apps, custom keyboards don't work if I reply from the lock screen, apps don't appear in the search query?
How can this be the "most advanced mobile OS" when the screen rotation doesn't work consistently, the music app skips as I switch between apps, custom keyboards don't work if I reply from the lock screen, apps don't appear in the search query?
Video Buffering
Any words from your source if the native video UI shows buffering progress again? This seems to have gone away with the release of iOS 8. The progress bar used to have a shading effect that would show how much has buffered and now there is no shading, it's just one solid color.
Any words from your source if the native video UI shows buffering progress again? This seems to have gone away with the release of iOS 8. The progress bar used to have a shading effect that would show how much has buffered and now there is no shading, it's just one solid color.
A problem occurred with this webpage so it was reloaded
"A problem occurred with this webpage so it was reloaded"
And reloaded, and reloaded, and …
I want this fixed. I have done all of the recommended fixes, and they have solved nothing .
That and the text selection function.
"A problem occurred with this webpage so it was reloaded"
And reloaded, and reloaded, and …
I want this fixed. I have done all of the recommended fixes, and they have solved nothing .
That and the text selection function.
Depending on how this turns out fixing long standing issues, this may be my last dance with the iPhone. I pay too much money to have a phone with these kinds of bugs. If I was on a cheap Android phone, I would understand, but not for $850 device.
How can this be the "most advanced mobile OS" when the screen rotation doesn't work consistently, the music app skips as I switch between apps, custom keyboards don't work if I reply from the lock screen, apps don't appear in the search query?
Music skipping is partly a RAM issue mixed with poor coding. iOS 8 has a lot of advancements going on under the hood and really 1Gb is such a bare minimum with so many new little processes going on behind the scenes.
My air 1 used to skip music a bit under iOS 8. My air 2 has done it once in 3 months. And I listen to music on it almost daily.
I've never worked in a highly structured software development environment but I imagine the guys working on iOS 9 are just working on the new features that will be implemented in iOS 9. It's not like multiple groups are working on the same features, or they're rewriting iOS from the ground up lol. That'd be inefficient and a waste of resources.
May be a waste of resources, but anyone knows working from a clean slate is always the best method. old code left behind,,, new features introduce cause of issue happening because the two don't always talk, weather as if its new from the ground up, u know its will take time, but u also know it will work out of the box.
I reckon Apple knows this too, but they can't do it because users want it out now. And instead rely, on fixing bits and pieces.... Basically picking out things from an already buggy and/or legacy OS.
Thus, basically means to me,,, no wonder why Apple has issues today.
I reckon Apple knows this too, but they can't do it because users want it out now. And instead rely, on fixing bits and pieces.... Basically picking out things from an already buggy and/or legacy OS.
Thus, basically means to me,,, no wonder why Apple has issues today.
Last edited:
We'll probably see iOS 8.1.3 rolled out publicly this coming week. I do think there will be an iOS 8.1.4 rolled out middle February 2015 before iOS 8.2 rolls out end of February, which adds Apple Watch support. And we'll see iOS 8.3 probably around early May 2015, which adds support for the larger screen of the iPad 12.2" version.
They'll probably release it with iPhone 6S(+), because this might be just as big as the
Watch event.
iOS is very modular, with lots of different components that can be worked on individually by different developers. Developers check out their module from the appropriate branch (8.1 or 8.2 probably, right now), work on fixing bugs are implementing features, and then check the modules back into the branch. For instance right now bug fixes will probably be checked into both 8.1 and 8.2 branches, where as feature additions will only be checked into the 8.2 branch.
Part of releasing the OS to the public involves unit testing on all the modules that have had bug fixes and feature additions, and then extensive testing on the branch that is going to be released. Once they are satisfied that there are few enough bugs in the release branch, it gets sent to us.
The fact that the developers are working on so many different versions of the operating system at the same time is one of the reasons why it is so hard to squash all the bugs. A bug might be fixed in the 8.2 branch simply because it was discovered when a new feature was being developed. So we won't see it until a point to comes out even though it is trivial to port the fix back to 8.1, and so on. A big issue is deciding whether to check work that was done on, say, 8.2, back into 8.1 to fix bugs. Since feature additions can introduce bugs, bug fixes can cause other bugs, and a bug fix on a lower branch can break a new feature added to a higher branch, it's a difficult job.
Disclaimer: this post was dictated into Siri so it probably has stupid errors in it. There's no way I'm typing all this crap out of my phone
These iOS releases have been getting buggier each year. I cringe when thinking about what potential headaches iOS 9 might bring.
----------
Haha, just wait until iOS 9 comes out! Then we're really in for it.
----------
Haha, just wait until iOS 9 comes out! Then we're really in for it.
I kind of what to go back to iOS 7. Or even iOS 6. When will they address the annoying bugs in iOS 8?
It's called shoddy journalism. Or they really don't want you to know so that you will think the data is more valuable than its really worth.
It is not the first time MacRumors has skimped on the math.
----------
Well, a good journalist would have said this up front instead annoying discerning readers.
Depending on how this turns out fixing long standing issues, this may be my last dance with the iPhone. I pay too much money to have a phone with these kinds of bugs. If I was on a cheap Android phone, I would understand, but not for $850 device.
How can this be the "most advanced mobile OS" when the screen rotation doesn't work consistently, the music app skips as I switch between apps, custom keyboards don't work if I reply from the lock screen, apps don't appear in the search query?
Or you could pay a lot for a nearly equivalent Android phone.... And have even more bugs... Or are you willing to go for 8.1 WP, that would be an original switch...
Or are you telling me those $200 buggy phones (because, yes, Android IS BUGGY) you'd have no qualms with are equivalent to the Iphone?
iOS is very modular, with lots of different components that can be worked on individually by different developers. Developers check out their module from the appropriate branch (8.1 or 8.2 probably, right now), work on fixing bugs are implementing features, and then check the modules back into the branch. For instance right now bug fixes will probably be checked into both 8.1 and 8.2 branches, where as feature additions will only be checked into the 8.2 branch.
Part of releasing the OS to the public involves unit testing on all the modules that have had bug fixes and feature additions, and then extensive testing on the branch that is going to be released. Once they are satisfied that there are few enough bugs in the release branch, it gets sent to us.
The fact that the developers are working on so many different versions of the operating system at the same time is one of the reasons why it is so hard to squash all the bugs. A bug might be fixed in the 8.2 branch simply because it was discovered when a new feature was being developed. So we won't see it until a point to comes out even though it is trivial to port the fix back to 8.1, and so on. A big issue is deciding whether to check work that was done on, say, 8.2, back into 8.1 to fix bugs. Since feature additions can introduce bugs, bug fixes can cause other bugs, and a bug fix on a lower branch can break a new feature added to a higher branch, it's a difficult job.
Disclaimer: this post was dictated into Siri so it probably has stupid errors in it. There's no way I'm typing all this crap out of my phone
Well, that's why we have regression testing (several level of it). If you introduce a small fix in a small branch and it unexpectedly breaks the main one... Well, those kind of head scratchers happen. Of course, regression can't catch what it doesn't test... So, its likely some side effect bugs will leak out, especially if Beta testing is not extensive enough.
Falso.
Usually all the changes are done on a main brach. Then there are other branches for example the 8.1.x branch. Safe, bug fixing commits get backported to the 8.1.x from MAIN