Did you restart?When I remove the iOS 16 Beta Profile, the search for iOS updates fails with „Unable to check for update“.
Did you restart?When I remove the iOS 16 Beta Profile, the search for iOS updates fails with „Unable to check for update“.
“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.
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.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.
1. Core function bugs 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
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.
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.
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?
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 wish there's some explanations why the bug happens. I mean activation, GPS, those are literally basic functions that have existed for decades.
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.
Sure, "software developer". Have a nice life.What I said is crystal clear.
Sure, "software developer". Have a nice life.
The sheer ignorance of people who claim to be software developers yet who likely haven’t stepped into a professional operation is staggering.
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.
It isn't in production.
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.
Since you seem to know so much better than them: Apple is hiring.
Kindly read the post I quoted and responding to. Hope that helps.
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.
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....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.