Every app I've tried has not crashed. I've had weird airplay volume issues... once.
I know, and you're right, but if these beta builds get in the hands of nearly all MacRumors readers as suggested in the original post, doesn't it defy the concept of non-public beta?
You are aware that 17.6 was released to devs, and goodly amount of devs are already utilizing 18 beta. So until this 17.6 beta is available to PB testers then the discussions won't be as active. For more comments see
forums.macrumors.com
I’m a dev, just not in Swift. The battery was annoying enough for me to at least try it. In short, my battery is much better again. I’ve worked in tech as a repair professional with Apple in my past life, so I’m more experienced doing this than the average user.
That is good news. Since Apple's software has become far more buggy under the so-called "leadership" of the clueless CEO Tim Cook, iOS versions finally begin to have some semblance of stability and reliability when the x.6 updates are released.
In my experience public beta are usually quite fine (I've noted a couple of minor but irritating problems with the current iOS 17 one and Apple News does not play well with it). But I wouldn't risk installing a developer one.I wouldn’t touch a pubic beta, either
This reminds me of the early days of them trying to brainwash us with that weird "you already know how to use it" tagline. My brothers and sisters and I found it hilarious and coopted it for so many stupid things.It's very usable, it just that the way you do things that are common place is now shifted around. Take for instance received calls. Clicking on the text of the caller doesn't initiate a call, only if you click on the phone icon on the far right. Clicking on the text opens the contact form with the ability to block or unblock calls from that party. In that manner it's like a bit of relearning is required with some features you use all the time. It not like a lot of the features they showed off have arrived yet which is typical that early in its cycle. At some point in the future most will have to learn all about how to use this rather then its becomes too featured all at once in Sept.
Well, the choice is "old stuff and buggy" vs "new stuff and buggy".
Yes, if you have a saved backup from 17.5 and are ok to DFU/restore your phone and then apply that backup. All your banking apps (and related wallet cards) will need re-authenticating.
When your Shortcut automations execute on iOS 18, can you disable the nagging Shortcut notifications on your Lock Screen? I have Shortcut automations on iOS 17 but can’t disable its notifications and it’s annoying!
Ah the crutch word again. It can be addictive to use “basically” as a non-descriptive filler. All software has bugs, it’s always been a goal to decease discernible bugs to a level where they cease to be noticeable, but it’s impossible to completely eradicate them all.
Well idk about all that but what I can speak to is my own personal experience which has been that, over the last several summers going back some 6 or 7 years now, the PB releases have historically been much more trustworthy to install on my daily driver irrespective of their test build (PB1, PB2, etc). Even in the years that had truly horrendous feedback regarding the volatility during the DB release cycle, generally speaking most of that got ironed out by the public testing phase. However, I think that's because Apple has gotten a much better handling on having their betas be closer to production-ready by time they start rolling them out to devs and the public alike.Stable only refers to a release that is unchanging such as the public release. Unstable means that a prerelease seed is always subject to its being changed. Usually the beta 2 sees additional changes/features added that were not ready for the WWDC seed. Beta 3 might see additional changes/features added. Honestly beta 1 is usually more solid then beta 2 or beta 3, with either being whats chosen as the first PB seed.
Ah the crutch word again. It can be addictive to use “basically” as a non-descriptive filler. All software has bugs, it’s always been a goal to decease discernible bugs to a level where they cease to be noticeable, but it’s impossible to completely eradicate them all.
But discussion of 17.6 ≠ discussion of 18.
I didn't think this was an issue on iOS17.... When looking at your automations, there's a 'Notify when run' switch you can turn off on iOS 18, -presuming this was there prior. Does that help?
How about if I just update to 17.6 with the current information that is on my iPhone at this time, rather then backing up from an old back-up that is not up to date as what is on my phone currently, can I still downgrade to 17.6 once the final version is released?
