Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
“Test this feature” in the release and their testers can’t get GPS to work? Probably a useful warning to them and their users is what I’m saying.

It is a build, not a release.
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.
Historically, Apple’s hardware teams have had latitude to fork parts of the system to prepare for an update. It is possible that for 16.0 and 16.0.1, the 14 and 13 have different source for their builds.

So this might be a new dual mode function which didn’t make for .0 - or it could just be an issue in the merge process happening for .1
 
Surprise surprise. Another release of software under Craig Federighi, another release of bugs & errors. This clown needs to be shown the door. Apple software has gone from best-in-class to worst-in-class ever since he took over.

Long gone are the days of "It just works".

Now it's "It just sort-of works. Kinda. We hope."
 
1. Core function bugs in production

It isn't in production.

Historically, Apple’s hardware teams have had latitude to fork parts of the system to prepare for an update. It is possible that for 16.0 and 16.0.1, the 14 and 13 have different source for their builds.

So this might be a new dual mode function which didn’t make for .0 - or it could just be an issue in the merge process happening for .1

I believe the merge typically happens by the "16.0.0" release for everyone not on the new devices. I.e., the iPhone 14 16.0.0 was an earlier build, but the 16.0.0 for everyone else already incorporates everything for it.
 
  • Haha
Reactions: Babygotfont
I wish there's some explanations why the bug happens. I mean activation, GPS, those are literally basic functions that have existed for decades. Why they are/were broken now, (beta or not)? What's being changed at the underlying level that break basic stuff like this? I mean if there's a fundamental change in the core of iOS, wouldn't it be great to know what it would be?
 
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.

If you state that core function bugs are not expected in beta, you either clearly have not worked as a software developer who has stepped into a professional operation, or you work for a toxic software company with unrealistic expectations.
 
Oh great, the “but it’s a beta” crowd again.

Betas are actually for devs to build and test apps before release. This is a pretty big impediment for testing GPS functionality as it’s one of the things that you can’t test well in the simulator, or down level versions if you’re developing against the newer APIs.

Beta Version
  1. “(computing) An early version of a program or application that contains most of the major features, but is not yet complete. Sometimes these versions are released only to a select group of people, or to the general public, for testing and feedback. This is the second major stage of development following the alpha version, and comes before the release candidate.”
 
I wish there's some explanations why the bug happens. I mean activation, GPS, those are literally basic functions that have existed for decades. Why they are/were broken now, (beta or not)? What's being changed at the underlying level that break basic stuff like this? I mean if there's a fundamental change in the core of iOS, wouldn't it be great to know what it would be?

The smallest changes in code can cause major features to break. You hope that automated and manual test coverage can get ahead of it, but that's just not realistic. Again, this is the point of beta tests. When you download and use the beta, you're essentially acting as the manual testers.
 
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

I've had an Android phone until just about yesterday, and have downloaded almost every Samsung One UI beta to my backup phone. They've had several bugs in their beta including some major ones which caused rollbacks and release pauses.


But I wouldn't dunk on them because again, these are generally expected in betas. It's test software.
 
  • Like
Reactions: MacCheetah3
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.

If bugs aren’t expected in a BETA then what’s the point of a BETA? Since you’re the Software Developer oracle here…

If you believe bugs don’t exist in software you’re either not a software developer or your a delusional…

If you’re not a developer you shouldn’t be on Development Betas. Just that simple. Obviously, this bug will impact developers working on functionality in this area, but that’s something developers expect in betas and will report to Apple and keep rolling on. After all, we know the process and how this all works.

If you are a ”normal user” just keep on keeping on. Things work for you.
 
  • Like
Reactions: MacCheetah3
If bugs aren’t expected in a BETA then what’s the point of a BETA? Since you’re the Software Developer oracle here…

If you believe bugs don’t exist in software you’re either not a software developer or your a delusional…

If you’re not a developer you shouldn’t be on Development Betas. Just that simple. Obviously, this bug will impact developers working on functionality in this area, but that’s something developers expect in betas and will report to Apple and keep rolling on. After all, we know the process and how this all works.

If you are a ”normal user” just keep on keeping on. Things work for you.

It's pretty obvious he is only pretending to be a software engineer.
 
If bugs aren’t expected in a BETA then what’s the point of a BETA? Since you’re the Software Developer oracle here…

If you believe bugs don’t exist in software you’re either not a software developer or your a delusional…

If you’re not a developer you shouldn’t be on Development Betas. Just that simple. Obviously, this bug will impact developers working on functionality in this area, but that’s something developers expect in betas and will report to Apple and keep rolling on. After all, we know the process and how this all works.

If you are a ”normal user” just keep on keeping on. Things work for you.

Bugs are expected... major flaws are not.
 
....and the fact that this particular issue is related to dual-GPS devices only makes it even more likely to have something occur. Gajillion lines of code affecting thousands of apps that use this feature. It will be fixed and my guess is fixed sooner rather than later. Despite being a beta, Apple won't wait the typical release cycle for something as important as this....16.1.1 incoming in days.
But it should be fixed by the time he official public version comes out so 16.1.1 shouldn't deal with the GPS issue
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.