Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

iOS 8.4 GM today?

mcfly88 said:
I don't know, just seems weird that they would introduce it in 8.4. Especially when they haven't tested it at all in the 8.4 betas.
Click to expand...
Wouldn't be the first feature they hold until a public release.

Beta is primarily for devs to test API changes. Things like SoundHound that tap into the Music app. A streaming music service tab has little to nothing to do with dev API. They can toggle that on after internal testing whenever.
 
I definitely think we could see a GM seed soon. But I do NOT think it will be today. My reason for this is: WWDC is too close, with rumors suggesting unveilings related to iOS 8.4 occurring there, for the GM to come out now. I suspect Apple will hold the GM until the keynote, release it post-keynote, and make it generally available the week after.
 
Futhark said:
Is no one else concerned about the length of time passed and no release to fix the unicode bug? When you find big flaws in the existing public release surely these need to be addressed as soon as possible never mind beta software?
Click to expand...
The beta isn't as important as the production version, but yes. I would not be at all surprised to see iOS 8.3.1 issued today with the bug fixed.
 
Futhark said:
Here's hoping? :) can I ask why you think today? I was hoping yesterday for maybe a new beta and an 8.3.1
Click to expand...
Just look at the history of iOS bug fix releases for guidance. You'll see what I saw. Anyway, Apple's historically released these emergency bug fix builds on non-Mondays @ 10:00 AM Pacific Time (or around then). This bug is important enough to warrant such a build.
 
  • Like
Reactions: Futhark
wrldwzrd89 said:
Just look at the history of iOS bug fix releases for guidance. You'll see what I saw. Anyway, Apple's historically released these emergency bug fix builds on non-Mondays @ 10:00 AM Pacific Time (or around then). This bug is important enough to warrant such a build.
Click to expand...

This is a bad bug. While your information on your phone is safe, the ease of which a DoS is caused should warrant an emergency patch ASAP.
 
  • Like
Reactions: sunking101
I7guy said:
This is a bad bug. While your information on your phone is safe, the ease of which a DoS is caused should warrant an emergency patch ASAP.
Click to expand...

I agree. Especially with news now that Apple's new music service may not launch until closer to the end of the month (and assuming iOS 8.4 would launch then too), that would be a long time to wait with such a serious bug in the software.
 
sunking101 said:
Why not release iOS9 now and consign this unfixable mess of code to the trashcan.
Click to expand...
Yeah.

Some time ago i came to the conclusion that seamless (not stuttering scroll) never will happen on iOS 8. It's that bad. That's why it's headed to a .4 iteration.

Bring on 9.
 
  • Like
Reactions: sunking101
part of me hopes they drop 8.4 GM with the unicode bug fix asap, but as long as its fixed in 9.0 beta 1 not really fussed :)
 
not really expecting any iOS 8 updates till next week at WWDC to be honest

why release an update this week and then release another the following week.
 
mattburley7 said:
not really expecting any iOS 8 updates till next week at WWDC to be honest

why release an update this week and then release another the following week.
Click to expand...
Perhaps to address an important bug, if they care enough about it.
 
  • Like
Reactions: Futhark
jeffUM said:
Forgive me, but is this really a bad bug? The average user will laugh about it with their friends and then move on with their day ...
Click to expand...
Of course it's a bug. The severity of it could be in question depending on who gets affected by it and how, but enough reports in various (long) threads about it that there are enough people who get affected negatively enough by it that it's rather far from a laughing matter for them.
 
C DM said:
Of course it's a bug. The severity of it could be in question depending on who gets affected by it and how, but enough reports in various (long) threads about it that there are enough people who get affected negatively enough by it that it's rather far from a laughing matter for them.
Click to expand...
Of course. But my take on things like this is similar to when I find a bad review on Yelp or in Google Maps: more often than not, only the really angry people will complain, and looking at a grouping of angry people can skew perception of the severity of the issue (how bad a restaurant is, how bad this bug is) - it's not always wise to assume that just because some people are angry, everyone is.

And, although I don't actually want to assume that Apple will always do what's best, I think they would've pushed an update by now if they *really* thought this bug was going to create a lot of problems for them. Possibly, the fact that we are anticipating larger releases at WWDC has created a period of time - as others have noted - in which the awkwardness of pushing of an update now actually creates a larger issue than the bug itself is currently posing.
 
jeffUM said:
Of course. But my take on things like this is similar to when I find a bad review on Yelp or in Google Maps: more often than not, only the really angry people will complain, and looking at a grouping of angry people can skew perception of the severity of the issue (how bad a restaurant is, how bad this bug is) - it's not always wise to assume that just because some people are angry, everyone is.

And, although I don't actually want to assume that Apple will always do what's best, I think they would've pushed an update by now if they *really* thought this bug was going to create a lot of problems for them. Possibly, the fact that we are anticipating larger releases at WWDC has created a period of time - as others have noted - in which the awkwardness of pushing of an update now actually creates a larger issue than the bug itself is currently posing.
Click to expand...
I agree that Apple certainly looks as to what impact it's all having and all that and makes a decision from their side of things.

That said, I don't follow the whole "angry" part and all that. Yes, not everyone will experience the issue, and yes, not everyone who experiences it would be truly badly affected by it, but it's been documented enough to show that if someone does get affected by it it's enough to cause at least a little hassle (about which I don't think the vast majority would be laughing about), and in enough cases to cause a bigger hassle. The exposure of this issue is likely what's one of the main gating factors for how Apple is going about it, not so much about how simply silly some people might find the issue if/when they encounter it.
 
people with beta 8.4, is the unicode bug fixed?
with a week of time that has lapsed, I'm beginning to think Apple has no idea how to fix this properly without some kludgey work around.
 
C DM said:
I agree that Apple certainly looks as to what impact it's all having and all that and makes a decision from their side of things.

That said, I don't follow the whole "angry" part and all that. Yes, not everyone will experience the issue, and yes, not everyone who experiences it would be truly badly affected by it, but it's been documented enough to show that if someone does get affected by it it's enough to cause at least a little hassle (about which I don't think the vast majority would be laughing about), and in enough cases to cause a bigger hassle. The exposure of this issue is likely what's one of the main gating factors for how Apple is going about it, not so much about how simply silly some people might find the issue if/when they encounter it.
Click to expand...

I consider myself fairly tech savvy and spend a good amount of time around here and I still don't know what this bug is about.

Anybody kind enough to briefly explain or provide a link? I'd be oh so grateful.
 
perkedel said:
people with beta 8.4, is the unicode bug fixed?
with a week of time that has lapsed, I'm beginning to think Apple has no idea how to fix this properly without some kludgey work around.
Click to expand...
There hasn't been an 8.4 beta (or otherwise) update since the discovery of that bug, so it's still broken there in the latest beta.
 
I always said that since iOS 8.4 dropped as a beta that it would be completely possible it would never hit the update block. I honestly think 8.4 was just a test of the new interface to not only see how people liked it but if it was stable enough. It will show up in iOS 9, but I don't think they will bring this whole new interface to iOS 8 especially if all devices that can run iOS 8 will run iOS 9.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back