iOS 16.4 Will Let You Specify an Apple ID to Use for Beta Access

[davethorp]

All of the websites formerly selling UDID slots must be rubbing their hands together that they are back in business now selling usernames and passwords for active developer accounts

There was literally nothing wrong with how things have been the last few years since Apple started doing public betas which shut down the UDID black market

 

[theotherphil]

But again, why do they still have a public beta program then? I'd imagine if Apple are turning people on betas away for hardware repairs, there'd be far more of those on public betas than dev betas.

I never said hardware support issues was the reason for the change, but one of the reasons. But you're also right - Apple will not replace hardware on devices with any beta OS installed, dev or public.

Here's a question though...Who's to say the next beta cycle is going to be the same as the last?

We're already seeing changes to the authentication method which may mean other changes to the program going forward.

By far the largest number of YT videos are on dev beta 1 & 2 - where certain individuals want the "me first" videos on the latest features of iOS, but these are usually still buggy. Look at all the comments and videos with regards to Stage Manager last year. Per the developer agreement, devs shouldn't be posting videos/ screenshots or discussing unreleased features that may be still buggy, and may or may not make final release.

In order to control this narrative, public betas may be limited in either content or releases going forward. I remember the early days of the developer betas where Apple actively pursued devs and issued takedown notices for breaches of the dev agreement.

Public Beta's don't usually hit until Dev Beta 3.

 

[jdclifford]

The first couple developer betas are often not made available as public betas. These initial betas may be very buggy which is why Apple only wants developers on them.

Over the years I found it is usually just when the initial beta is released after WWDC that there is a gap of a few weeks b4 the 1st PB is released. After that it’s usually only 1 day between DB and PB releases. My point was that no matter which beta Apple makes u use, the “SUPPORT BURDEN” should be the same as to bug report volume being filed.

 

[Computers 4 U LLC]

This is exactly the truth - and probably one of the reasons Apple made this change. Upset customers in their store needing repairs (battery or screen replacement for example) which have been denied.

I took one of my older testing iPhones into an Apple Store to have the battery replaced. They told me I had to install a current release OS as their testing software suite is only valid against current release OS.

They scan the entire device for errors before even replacing a battery - likely so they are not blamed for any subsequent issues after the battery replacement.

Not true, I have had plenty of devices repaired by Apple that have had beta software installed on them and have never had to switch to a current non beta version.

 

[_Spinn_]

This is good for those with separate Apple IDs.

 

[theotherphil]

Not true, I have had plenty of devices repaired by Apple that have had beta software installed on them and have never had to switch to a current non beta version.

I dunno what to say man, I'm a dev and I've tried to have my screen/ battery replaced and my wife has tried to have a warranty repair on the top speaker. In both cases the Apple Tech stated that their diagnostic software lacked support for the beta I was on and that I had to reinstall the latest publicly available GM.

Running Apple Services Toolkit is mandatory before they can order parts. RepairCAL is the tool used to re-enable batteries, screens, TouchID and FaceID after repairs. If those tools lack support for the latest dev beta, I'm not sure how you expect them to perform a repair.

Another forum user also posted earlier in the thread that they've had the same issues when presenting for repairs with a dev beta installed. So I respectfully say, you may have gotten lucky that the diagnostic software had been updated at your local Apple Store. This cannot be guaranteed.