Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Lol y’all argue too much. Acting like Apple reads this. If you don’t like the bugs. Stay off the betas. Let’s see discussions on topic.

I remember bugs use to annoy me but I accept that.

If you don’t like bugs, don’t use Betas. It’s as simple as that in my opinion. I don’t see what’s wrong in suggesting this. Anyway, back on topic...
 
  • Like
Reactions: clavain and Ossyref
Anyone having an issue with iMessage?

Photos being received get stuck on downloading and do not display.

Tried a restore but issue remains.
 
Lol y’all argue too much. Acting like Apple reads this. If you don’t like the bugs. Stay off the betas. Let’s see discussions on topic.

I remember bugs use to annoy me but I accept that.
Of course, someone at Apple reads this. Between here and Reddit, they probably get more good feedback than all the bug reports they get.
 
Just checked on my XR and it does crash Safari for me too. Just tried macrumors.com and it was good but if you add the forum.macrumors.com then it crashes on the c.
Also happens on my XS. Bookmark works perfectly fine though. It's been years since I've had to type out that address.
 
The Music app has been freezing a lot since downloading this beta. Basically locks up to the point that you have to force quit and reopen it.
Just had it randomly quit. I used to have these kinds of problems in iOS 11 a lot. Things like adding too many songs to the queue would completely freeze the music app and at times the entire phone. If this persists I am going to have to downgrade, unfortunately. Sucks because the only reason I upgraded to this beta was to get the new look in the For You section of Apple Music.
 
Can I restore from a beta 3 backup if I downgrade to beta 2? This Safari crashing issue is annoying.
Why would you want to restore? If you are using an IPSW to revert back to beta 2, it will just install it and you'll be good to go thereafter.
OR do you mean you do a clean install? :)
 
Why would you want to restore? If you are using an IPSW to revert back to beta 2, it will just install it and you'll be good to go thereafter.
OR do you mean you do a clean install? :)
Oh I meant restore from an iCloud backup. I thought that was the only way to downgrade. But you’re saying I can just click update while holding option and select the beta 2 ipsw?
 
Oh I meant restore from an iCloud backup. I thought that was the only way to downgrade. But you’re saying I can just click update while holding option and select the beta 2 ipsw?
I'm sure a few ppl will correct me here, however, I have downgraded a few times over the life of these betas and yes, I always use the IPSW file just as you suggested in your comment
 
That's not what I understood the letters to mean. It was explained here in the forums that the letter at the end of the number signifies how many times it ran through internal QA before the build was released outside Apple.

And, historically, it's been my experience with iOS that the higher number of retries after a build has been made, the less polished it is as a result. A good example is the Safari bug we found earlier today. It wasn't there in Beta 2, which was a (d) build, but it showed up in this one.

This build had to go back once more through the QA cycle than Beta 2.

But the alphanumeric characters at the end of the build are QA iterations. What you are talking about is the number part before that (build). When a version ends with „a“ it passed QA on the first try, „e“ means it took 5 tries with 4 „bug fix iterations“. Has nothing to do with features being pushed in, the build is already locked.
Not talking about the build number. But this is typically how betas work. They are not progressive. So things that worked in beta 1 or 2 may not work in beta 3 and that is normal. The final will have all changes merged and will work again. Potentially for example, in this particular beta they may have been working on some specific changes to Safari to be tested. (Turns out its not working to well it would seem.) Could be that it took several commits (a,b,c,d,e) to get that code like they wanted plus other changes other folks may have been working on. (other separate items/features/changes/bugs) In later builds there is less of this sort of thing going on and just fine tuning and optimizing things before release version so a or b letters usually.
 
  • Like
Reactions: gwhizkids
Yeah usually the betas have bugs but this was has more than usual. We all addressed the Safari one already but my phone crashed and rebooted itself while in music. For those that haven't installed yet, wait it out. I bet apple releases an update before week's end.
 
  • Like
Reactions: H3LL5P4WN
Modem firmware jump from 3.55.00 to 3.60.01 on Qualcomm iPhone 8/8 Plus/X.

Does this help with anything noticeable ?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.