Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Dev beta is so app makers can get an early jump on making sure their apps work with what's coming out, but it seems more and more public beta release runs so close they may as well just do one beta release.
My guess is that the first beta is to ensure that it won't brick your device. Once Apple is sure of that, they will then seed to the public beta to everyone else. More of a precaution than anything else.
 
  • Like
Reactions: SFjohn and Sciomar
My guess is that the first beta is to ensure that it won't brick your device. Once Apple is sure of that, they will then seed to the public beta to everyone else. More of a precaution than anything else.
It’s interesting that alpha testers did not catch this, unless there just aren’t a lot of alpha testers using the 14 pro. I don’t know how their internal design teams are fielded. Their focus could be elsewhere also, GPS and maps aren’t as pressing I guess.
 
It’s interesting that alpha testers did not catch this, unless there just aren’t a lot of alpha testers using the 14 pro. I don’t know how their internal design teams are fielded. Their focus could be elsewhere also, GPS and maps aren’t as pressing I guess.
If they are testing inside Apple HQ, that might imply a more sedentary role (ie: they are confined inside a computer lab, and not moving around a city), and bugs based on features such as GPS and Maps may be harder to catch. That's just my guess at least.
 
It’s interesting that alpha testers did not catch this, unless there just aren’t a lot of alpha testers using the 14 pro. I don’t know how their internal design teams are fielded. Their focus could be elsewhere also, GPS and maps aren’t as pressing I guess.

It seems that it is working for some iPhone 14 phones, so I can see how this can slip through testing. Again, this reinforces the benefits of a beta.

And reading that thread, it's unbelievable to me how many people use beta software on their main devices, just to have the latest and greatest. I mean there was an Uber driver using the beta on their phone used for navigation. Jesus.
 
  • Wow
Reactions: SFjohn
It’s interesting that alpha testers did not catch this, unless there just aren’t a lot of alpha testers using the 14 pro. I don’t know how their internal design teams are fielded. Their focus could be elsewhere also, GPS and maps aren’t as pressing I guess.
Alpha testers leave their office/basement/bedrooms? 😂😂 ... kidding guys. don't flame me 😃
 
  • Haha
Reactions: Sciomar
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.

And it would be perfectly fine if it was just legitimate complaints from devs about disruptions to their work, but a lot of people install betas onto their personal daily use devices and then complain when a feature doesn’t work right.
 
Last edited:
This is why betas should not be used on one's personal devices. Of course, that won't stop folks from doing so.
Yeah, it’s a bit baffling that folks don’t understand what beta means. It’s ok to install it on one’s personal main device, but don’t complain about it when the software has major problems. It’s a beta! 😂🤔
 
  • Like
Reactions: MacCheetah3
Yeah, it’s a bit baffling that folks don’t understand what beta means. It’s ok to install it on one’s personal main device, but don’t complain about it when the software has major problems. It’s a beta! 😂🤔
Yeah it’s beta, but betas that goes out to third-party devs should not render key hardware features completely useless, that’s a show stopper.
 
Last edited:
  • Like
Reactions: xgman
Also the home screen doesn’t let you swipe left or right at all. After I reboot the Home Screen works for about 2 minutes or less and than stops letting me swipe left or right.
 
  • Like
Reactions: rdinterman
iOS 16.0 - Bug for activating. IOS 16.0.1 (day one update required). IOS 16.1 bug… not a great start.
No problem activating I used Quick Start, I was on my private Wifi — public Wifi was where the activation bug might occur and then after that I updated to 16.01 no problems. I would not ever try a beta that soon on my new phone but have not been testing betas since before last years 13 ProMax arrival anyway
 
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.
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.
 
Lol what? The battery draining makes phones unusable
Not experienced battery drain. Only experience I am seeing during the install and then afterwards indexing and installing apps which can take sever hours or more if you have a lot I do see phone getting warm on my magsafe puck and some weirdness so i went to lighting — it stayed at 74 percent until that was done and cooled down then charged back up normally. Next day flawless battery use and i was on it most of day really over using it compared to what will be regular.
 
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.
Sounds like you have extensive coding experience. What programs have you written? I'd like to buy one and see what a really great programmer can do. Thanks.
 
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.
 
  • Like
Reactions: Solomani
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.