Makes you wonder about the emergency satellite accuracy and/or functionality!
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.
Warning: iOS 16.1 Beta Breaking GPS on iPhone 14 Pro Models
- Thread starter MacRumors
- Start date
- Sort by reaction score
Apple better include a gun and a bullet in the iPhone’s box, that way people at least can mercy themselves instead of placing hope on something that isn’t reliable to call for rescue.
Last edited:
I think lately the Beta's are Alphas and the public releases are the Betas
Yeah sure, just a déjà vu...
Apple yanks iOS 8 update after crippling iPhone 6 and 6 Plus
Apple today released, then quickly yanked, its first update for iOS 8 after customers flooded its support forum with reports that their iPhone 6 and 6 Plus smartphones could no longer connect to a cellular network.
www.computerworld.com
I just got the iPM 14 this Friday.
I enjoy the new fresh battery and beta is not something I would like to enjoy for the next year.
Not worth jumping in betas with new devices unless you are a developer or you just can afford yearly hw upgrades.
But that is just my PoV.
I enjoy the new fresh battery and beta is not something I would like to enjoy for the next year.
Not worth jumping in betas with new devices unless you are a developer or you just can afford yearly hw upgrades.
But that is just my PoV.
That’s a lazy development attitude. It compiled so put it in beta for unit testing.
The whole point of the Public beta program is for end users to test and find the small bug that was missed. The whole point of it being delayed from the dev beta is supposed to be catching massive game breakers first.
Core function failures are not expected in beta and when they happen it’s a development embarrassment.
And, since the program began, Apple has outlined/reminded/warned beta software is for testing as well as recommends such testing be done on a secondary, non-critical device.
Apple said:
Apple Beta — FAQ
Yep. SMH “Stupid is as stupid does."
I no longer have that uncontrollable craving to try stuff out as soon as possible. I waited until the .3 release — well, .4 on the Watch because Apple mysteriously skipped watchOS 8.2 — last OS round and plan to do the same again. Nor do I have extra devices or time to help Apple test. The (Public) Beta program is absolutely useful, but it’s not something everyone should jump into.
And while unfortunate at times, Apple’s beta versions are part of the same process (i.e., Apple and third-party app devs are building and testing simultaneously) — or at least third-parties intending on concurrently launching their up-to-date app version(s) with the up-to-date OS versions.
It’s not whether somebody will make a mistake, the key is how well they respond.
My complaints on this are:
• Parallel programming has productivity benefits. However, it’s a challenging puzzle and, in my opinion, platforms like Git are not a good enough solution, the process is still clunky, convoluted, and fails to prevent a lot of problems.
• Automation can add efficiency. Although, (again) in my opinion, software developed to test software is no match against genuine user experimentation. One of the lessons I will not forget is “expect user input to be any and everything."
Ultimately, there have been too many cut corners in development simply because they (e.g., testing) don’t appear to help the financial sheets — of course, this spreads far beyond Apple.
What is there to apologize for? Here is beta software. Here are stupid people who install this beta software on production devices. Hilarity ensues.
Nonsense. Core function failures even happen in production. It's expected that betas will have bugs and will break; that's the entire point of them. They're experimental by nature. Beta failures will occur in startups and the biggest of companies; it's why betas exist. There is a specific reason why people are warned not to install beta software on main devices; it is for bugs like this.
The sheer arrogance of people who likely aren't even software developers is staggering.
We can only speculate, but one clue: the iPhone 14 Pro has a significant change to the GPS by being dual-frequency. That the bug doesn't affect the non-Pro 14 suggests this may be relevant.
So what kind of change could it be? It could be relatively low-priority, like performance and/or battery life improvements. They didn't merge it into 16.0.0 for that reason.
Or, it could be higher-priority, like a workaround for a different bug. Maybe switching frequencies is broken on Galileo but not on GLONASS.
They all have mostly the same code base. Otherwise, Apple would have to ship dozens of different entire iOS systems for the Simulator.
I mean, yes, how else could this possibly work?
Why on earth are you assuming they made a code change in an area they didn't intend to make a change in? That doesn't even make sense. Like, how does that even work? Someone shows up drunk and edits the wrong file?
Of course 16.1 is a massive code merge. Not as massive as 16.0, but still fairly significant.
I bet you've never seen a software project at remotely the scale as iOS.
How many times does it have to be said? Don't put test software on your personal phone.
The beta is the process of quality control. These complaints about quality of software are the very silly.
1. Core function bugs in production damages company and developer/development team reputations.
2. Core function bugs are not expected in Beta.
3. The sheer ignorance of people who claim to be software developers yet who likely haven’t stepped into a professional operation is staggering.
Imagine how much you’d be dunking on android if same thing happened with one of their public betas
You don’t need to be a software engineer to LOL at a glaring bug affecting tons of basic functionality
Just saying