Of course, I'm a dev... I always need to make sure my apps will work on major releases...You’ll be back, honey 😌💅
Of course, I'm a dev... I always need to make sure my apps will work on major releases...You’ll be back, honey 😌💅
I don’t think basic functionality should be part of the beta though. That’s like starting from square 1. And if you know basic functionality like gps location doesn’t even work, why would you release it?As a software engineer for almost 25 years, I firmly blame google for this.
No, honestly. They’re the ones who redefined “beta” in the public consciousness to mean “newest cool thing” when in reality (and this was well understood before that) it meant “feature-complete, but probably unstable; needs thorough testing prior to release.”
Beta is the “shakedown cruise” of software. You wouldn’t build the first of a newly designed class of ocean liner, and then pack it full of cruising tourists for its first trip out of dry dock. You take it out for a shakedown cruise first, without passengers (and before anyone says, “but some cruise ships do a shakedown with passengers for a discount!” Yes, that’s sometimes true… that would be the Public Beta in this analogy) to test the ship’s systems, seaworthiness, make sure the crew knows how to do their jobs, etc.
Yeah from what I am reading it is a troll fest of folks justifying their non apple phones being better LOLQueue the Apple haters. Their best day ever.
I don’t think basic functionality should be part of the beta though. That’s like starting from square 1. And if you know basic functionality like gps location doesn’t even work, why would you release it?
Yeah. I was noticing this yesterday in my car. I also have an issue myself where I swipe right to the App Library and all the icons overlap with the other pages too.Glad OP posted this, as my iPhone 14 Pro on 16.1 is definitely experiencing this. Major bummer! Sure Apple will fix quickly.
For those saying “it’s just a beta”
Severe bugs affecting the “release” non beta on the iPhone 14 pro.
![]()
Apple Investigating iPhone 14 Pro Models Freezing After Data Transfers
Apple is investigating a bug that may cause iPhone 14 Pro and iPhone 14 Pro Max models to freeze after customers transfer their data from an older...www.macrumors.com
Yup. Once I saw the title of the thread, I knew about 85% of comments would be Apple hate. It's just the nature of MR now. I figure if all one can say is hateful things, they are very unlikely to make any meaningful contribution I found that taking full use of the ignore list will help. About 50 added so far. So many to go. If I'm kicked off for my comments, it wouldn't bother me. I'm find with just reading the articles (which overall are quite good) is really enough. I'm getting tired of sifting through tons of hate just to get that one tiny little morsel of useful information.Yeah from what I am reading it is a troll fest of folks justifying their non apple phones being better LOL
Stop defending Apple. When this is rhe case they have put the bugs in the beta release notes so devs are aware of it and to not report these issues. If Apple released it without such notes then they were not aware of it which speaks volumens pf their QA divisionBecause there are other areas of the os that need developer scrutiny. I’d hazard a guess that there are vastly more developers writing apps that have zero interaction with GPS than those that do. And those developers need access to the beta to make sure their apps still function correctly and either make changes or file bugs so Apple can fix errors before the beta moves to GM.
That is the only purpose of the beta: to ensure that the GM release goes as smoothly as possible, and that only happens when bugs are found.
If you are running a developer beta for any reason other than to find bugs (in Apple’s software, or in your own) then you’re running it for the wrong reasons.
And with the brand new (to Apple) GPS technology in the iPhone 14, GPS bugs in early betas should be expected.
The more morons you hire as programmers and managers, the more crap you get in the OS.
I'm the CTO of a large org who wants his developers to be productive and has to plan for supporting 16.1 and not being able to get our release cohort of external testers on 16.1 to get GPS features, well, is understood as a risk in the process, but is worthy of discussion. We don't release until 90% of external cohorts on our supported platforms are passing tests, and seeing a huge red on an entire suite of tests for 16.1 it's a REALLY useful thing to know that this is an AAPL issue and not something in my org's code issue. And, no, I don't read every release note of our own software let alone everything in my stack. I wish I had that kind of time, but I don't, and anyone with any level of scale/management has the 24 hours in a day issue, so it was really nice to get this warning and discussion so I (and others in my boat) know what the red is.wouldn’t you be apart of the pretend developers crowd that don’t actively test and send reports? 🤷♂️
i think there was an article on here some time ago that only 0.5 % of beta testers actually test and report.
And that's my point: the "it's a beta, shutup" crowd is actually the "pretend" professionals who don't fully understand the nuance of how software at scale is built, written, and released.
The quality of apps you download (and/or the speed with which we can support new features at or near release) is *directly* correlated (and causatively linked) with the quality of betas we get.Never hop on even Versions of iOS. It's a rule.
I agree to an extent. I just don't think they've hired morons, I think they've hired very smart people who know how to do the bare minimum and still get bonuses and great stock performance because they work at an enormous company with no actual real, meaningful competition in the market place and a walled garden hold on the market they own.The more morons you hire as programmers and managers, the more crap you get in the OS.
I agree to an extent. I just don't think they've hired morons, I think they've hired very smart people who know how to do the bare minimum and still get bonuses and great stock performance because they work at an enormous company with no actual real, meaningful competition in the market place and a walled garden hold on the market they own.
Not a good story if you truly believe in free markets, capitalism, and market forces because we've gone to the other side of the spectrum from overly regulated, planned economies to, well, stifling innovation before it can even get started.
Never hop on even Versions of iOS. It's a rule.
Agree 100%. In the US enough of my country people have been convinced (largely by oligarchs themselves) that somehow government is always bad, and "free markets" (unregulated capitalism) is the only solution that we're basically giving our government away to private industry as its enablement arm.Not a place for the tangent. I guess.
But the course of capitalism is to stave off competition and choke itself to death. The only way to actually have a healthy and functioning free market is to have robust and well enforced regulations to keep it from doing so. Adam Smith explained this all in The Wealth of Nations published in 1776… Considered the Bible of Capitalism.
Quality control or lack thereof is the relevant theme. Apple apologist.And that’s relevant to this bug because…?
People need to ask themselves if they truly understand the entire point of a company releasing beta software… You literally have to AGREE that you know there’s a chance that things could be broken and are told NOT to install it on a device needed for daily use.For those saying it’s a beta, I’ve used betas before that didn’t have a gps problem.
Apple’s software quality control has declined, as shown from:
I know bugs exist in software, and Microsoft has its share of serious issues, but some of apple’s bugs are severe.
- Various severe Monterey bugs (in some versions of Monterey, I had hard kernel panics when a tb4 dock was connected to my M1 Max MacBook, and the Mac woke from sleep… a problem I never experienced on any other OS except for Monterey)
- stage manager bugs in iPadOS/Ventura.
- iOS 15.0 (initial point release) bugs with pairing an Apple Watch.
- iOS 16.0 bugs with activation of iMessage/FaceTime.
- All the 0 days in Monterey and iOS 15.
- Monterey also had bugs with the firmware update process, and was bricking some M1 Pro/max laptops.
And we, the apple community, should demand more from apple. Especially since apple is raising the price of its devices (outside the USA).
I agree, however, my (and I think most others) reminder “it’s a beta” is a response to comments such as:I'm the CTO of a large org who wants his developers to be productive and has to plan for supporting 16.1 and not being able to get our release cohort of external testers on 16.1 to get GPS features, well, is understood as a risk in the process, but is worthy of discussion. We don't release until 90% of external cohorts on our supported platforms are passing tests, and seeing a huge red on an entire suite of tests for 16.1 it's a REALLY useful thing to know that this is an AAPL issue and not something in my org's code issue. And, no, I don't read every release note of our own software let alone everything in my stack. I wish I had that kind of time, but I don't, and anyone with any level of scale/management has the 24 hours in a day issue, so it was really nice to get this warning and discussion so I (and others in my boat) know what the red is.
its Apple. Software quality control has been terrible for a while now.
Sometimes I wonder if the employees even use iPhones and iOS
Give me a break. Just what amazing code change caused the GPS to break? You know how this happens? Garbage quality code management. They have had a growing problem with this for YEARS and it’s only gotten worse with every additional branch they create with deviations from a standard code base for all iOS devices and then with multiple teams running in tandem developing in parallel. Obviously someone did a bone headed code merge that replaced functional code with non-functional code in an area that likely wasn’t even touched for any reason in the beta.
They should be working on code changes only in the areas they are actually intending to implement changes. Not doing massive code merges that inadvertently overwrite functional code with redundant code.
This is software dev 101 and ANY mature shop will know how to do this. This wreaks of a half baked operation.
Right. Did Apple even test this on their flagship before release?
I have no doubt Apple has some lazy or burned out employees in which the fault is on those individuals. However, from what I’ve seen, even beyond this industry, the problem is top-down: get there first and worry about quality later. The “space race” mentality, if you will.I think they've hired very smart people who know how to do the bare minimum and still get bonuses and great stock performance because they work at an enormous company with no actual real, meaningful competition in the market place and a walled garden hold on the market they own.
More issues: https://www.macrumors.com/2022/09/18/iphone-14-pro-camera-shaking-vibrating-issue/People need to ask themselves if they truly understand the entire point of a company releasing beta software… You literally have to AGREE that you know there’s a chance that things could be broken and are told NOT to install it on a device needed for daily use.
They expect there to be issues and count on the beta testers to encounter the bugs they didn’t know about & help identify what caused them by submitting coherent bug reports.
If the initial and dominating response is to complain about software quality then you are missing the point.