iOS 26 Beta 2 ― Bug Fixes, Changes, and Improvements

[StumpyBloke]

Too many people here are forgetting this is a developer beta, not a public beta, a developer beta.

If anyone is using this as their only phone (daily driver) then they take all the risks that come with that and have absolutely zero right to moan about it. The whole point of a developer beta is to report all of these bugs to Apple, and that there can and likely will be serious bugs.

 

[Stiille]

How would most of these bugs be found if not installed on a daily driver?

How would people know that they can’t get incoming calls from unknown numbers? Even with the settings turned off and on, phone reset, etc.

Second phone number for just testing things? 🤣

As all the others said already, stop moaning about bugs, heat, crashes and not working stuff ! It’s the second beta of maybe 8 or more !
Don’t expect that things will work as intended !

And as @StumpyBloke said, no right to moan! You know the risks if you install it on daily driver !
I did a rollback to iOS 18.5 because to much heat on my 15 PM , now I am „patiently“ waiting for the official release mid September!

 

[HouseLannister]

no right to moan!

Being on the internet gives you the right to moan. It’s the web’s sole purpose.

 

[dannyyankou]

Seems like music added on my Mac running macOS 15.5 isn’t showing up on my iPhone on iOS 26b2. My iPad seems to be updating, and even looking at Apple Music on the web I’m seeing music I’ve added. Just my iPhone not working.

I'm having similar issues syncing between Tahoe and iOS 26. It seems like clicking "Update Cloud Library" in the Music app on the Mac forces the iPhone to update.

 

[hovscorpion12]

How would most of these bugs be found if not installed on a daily driver?

How would people know that they can’t get incoming calls from unknown numbers? Even with the settings turned off and on, phone reset, etc.

There's a reason why its called a developer beta. It's designed only for registered developers to test their apps against the OS and report back

With Apple's recent move to make the developer account free, it resulted in both developers and public users to download.

The general recommendation every year is never install a beta on your everyday product, but rather a secondary product. [hence developers having multiple devices to test].

The public beta is designed for the general public to use. That is where Apple starts to pay attention to the general public + Devs feedback.

 

[srbNYC]

But my god, it’s a piece of trash update. Phones running hot, AirPods not connecting, etc. are all basic things that shouldn’t break with the NINETEENTH release.

Interesting. I'm not having any of these issues. Doesn't make me an Apple apologist.

 

[dwrufus53]

The amount of Apple apologists in this thread is crazy. Yes, it’s a beta - of course it’ll have some bugs and glitches.

But my god, it’s a piece of trash update. Phones running hot, AirPods not connecting, etc. are all basic things that shouldn’t break with the NINETEENTH release.

It's kind of what happens when one has unrealistic expectations for a first or second beta on their primary device. As a retired coder, I can state with 100% certainty that solid code (there's no such thing as "perfect" code) can often get FUBAR with subsequent changes and evolutions. The fact that this is the "NINETEENTH release" of iOS notwithstanding, this is developmental code. As such, it's not intended for daily use on your primary device, and problems, even show-stopping, scorched earth problems are possible. Expect nothing less.

 

[Stiille]

It's kind of what happens when one has unrealistic expectations for a first or second beta on their primary device. As a retired coder, I can state with 100% certainty that solid code (there's no such thing as "perfect" code) can often get FUBAR with subsequent changes and evolutions. The fact that this is the "NINETEENTH release" of iOS notwithstanding, this is developmental code. As such, it's not intended for daily use on your primary device, and problems, even show-stopping, scorched earth problems are possible. Expect nothing less.

Amen 🙏

 

[gank41]

I'm having similar issues syncing between Tahoe and iOS 26. It seems like clicking "Update Cloud Library" in the Music app on the Mac forces the iPhone to update.

Not for me :-(

 

[Broken Hope]

Not sure what triggers it but performance on beta 2 sometimes feels like it’s at 30 FPS and I have to restart my phone to resolve it.

Hopefully beta 3 is better.

 

[cane811]

There's a reason why its called a developer beta. It's designed only for registered developers to test their apps against the OS and report back

With Apple's recent move to make the developer account free, it resulted in both developers and public users to download.

The general recommendation every year is never install a beta on your everyday product, but rather a secondary product. [hence developers having multiple devices to test].

The public beta is designed for the general public to use. That is where Apple starts to pay attention to the general public + Devs feedback.

Is it developmental code? Because so was Apple Intelligence last year and that still hasn’t been implemented as promised.

Apple’s been slacking in fit and finish lately regarding software - beta or public release. Let’s call a spade a spade.

 

[WildstarBR2020]

And yet they break every year. I don’t think this beta is any worse than the last five years around the end of June.

But I do think Liquid Glass is an issue that won’t be fully fixed by September.

I agree. The whole concept of this new design framework is… not pleasant. It’s no “glass” - when you play with the phone interface switching between “Favorites”, “Recents”, etc, it’s easy to feel the interface is more a “Jelly”, “Gooey” than “Glass”. Maybe I’m so used to interact with “firm”, “defined” and “firm” UI elements that this “organic”, “soft”, “mushy” interactions give me the feeling it is not accurate ou it will behave different we think of…

 

[WildstarBR2020]

Interesting. I'm not having any of these issues. Doesn't make me an Apple apologist.

The only thing that… not exactly “bothers” me, it’s more “worries me”, it’s how hot the iPhone is getting specially when recharging during the night. I’m even putting it in the small fridge we have in the bedroom when recharging…

 

[d245770q]

I agree. The whole concept of this new design framework is… not pleasant. It’s no “glass” - when you play with the phone interface switching between “Favorites”, “Recents”, etc, it’s easy to feel the interface is more a “Jelly”, “Gooey” than “Glass”. Maybe I’m so used to interact with “firm”, “defined” and “firm” UI elements that this “organic”, “soft”, “mushy” interactions give me the feeling it is not accurate ou it will behave different we think of…

Purely subjective! But thanks!

 

[d245770q]

The only thing that… not exactly “bothers” me, it’s more “worries me”, it’s how hot the iPhone is getting specially when recharging during the night. I’m even putting it in the small fridge we have in the bedroom when recharging…

“Worries me”. Why be worried? It’s on your app developer phone, right?

 

[Stiille]

The only thing that… not exactly “bothers” me, it’s more “worries me”, it’s how hot the iPhone is getting specially when recharging during the night. I’m even putting it in the small fridge we have in the bedroom when recharging…

My iPhone 15 PM with iOS 18.5 gets hot while charging too, I think it’s the summer temperatures at my location

 

[drak22]

Apple Pay doesn't display or store payments. The payment actually goes through, but it doesn't appear in the app. Yesterday at noon, I paid with Apple Pay, and it's been almost 24 hours and the transaction hasn't appeared. I've reported it to Apple because this behavior is very common for me, but on other occasions, the payment would appear in the middle of the night. This time, I don't even wait for it to appear. In beta 1, it worked without problems, so it seems to be the same as always, alternating between versions where it works and then one that doesn't; the next version doesn't work again, and the next one does, and so on.

 

[HouseLannister]

It’s on your app developer phone, right?

Just stop with the shaming, already. Such passive-aggressive bullying.

 

[DennisdeWit]

“Worries me”. Why be worried? It’s on your app developer phone, right?

“Oh, you are not a developer? Why are you installing a developer beta when you are not a developer? It is not meant for you.”

In some way that way of thinking seems very entitled and passive-agressive. And I am telling you that as a developer. Let people have their toy.

 

[zencowboy]

I've notched in Kindle app and the text-to-speech...it reset my voice option back to the default old Siri voice. And now for the life of me cannot find where or get it to change to a more human voice.

 

[Stiille]

I've notched in Kindle app and the text-to-speech...it reset my voice option back to the default old Siri voice. And now for the life of me cannot find where or get it to change to a more human voice.

Settings -> Apple Intelligence & Siri -> Voice

 

[d245770q]

“Oh, you are not a developer? Why are you installing a developer beta when you are not a developer? It is not meant for you.”

In some way that way of thinking seems very entitled and passive-agressive. And I am telling you that as a developer. Let people have their toy.

Each to their own… let them have their toy… but don’t moan when their toy isn’t actually ready for you, but you purchased it anyway!

 

[ExAndroidUsr]

Too many people here are forgetting this is a developer beta, not a public beta, a developer beta.

If anyone is using this as their only phone (daily driver) then they take all the risks that come with that and have absolutely zero right to moan about it. The whole point of a developer beta is to report all of these bugs to Apple, and that there can and likely will be serious bugs.

Yep this is crystal clear. I love to live dangerously and I use it on both my secondary and my primary phone LOL.

 

[dwrufus53]

Yep this is crystal clear. I love to live dangerously and I use it on both my secondary and my primary phone LOL.

I have stated all along that if you fully understand the risks and pitfalls of running an early beta of a x.0 software release, go for it.

I also have some caveats for those who choose to do so:

• Understand the risks.
• Make a good full backup of your data.
• If (when) you find bugs, report them to Apple va the Feedback app.
• Share what you find with the community in terms of bugs, issues and shortcomings.
• Don't b*tch and moan when stuff breaks, because stuff will break.
• Whatever you encounter, it's not the "worst version of iOS ever created".

 

[HouseLannister]

• Whatever you encounter it's not the "worst version of iOS ever created".