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.
Probably right, would make no sense having 14.8 with a security fix, then release 15 without those same security fixes.
It also means the new iPhone 13’s will get a day 1 update. 15.0.1, maybe exclusive to them, or maybe for all devices if Apple fix the music bug that people have mentioned.
 
  • Like
Reactions: Samdh90
It also means the new iPhone 13’s will get a day 1 update. 15.0.1, maybe exclusive to them, or maybe for all devices if Apple fix the music bug that people have mentioned.
I saw someone mention that the music bug was fixed in the public bit. Per IPSW, it looks like the iphone 13 will get todays build as well, if not, they might have already had it to begin with. Looking at IPSW, the first build and first beta build both aligned with: 19A346
 
I saw someone mention that the music bug was fixed in the public bit. Per IPSW, it looks like the iphone 13 will get todays build as well, if not, they might have already had it to begin with. Looking at IPSW, the first build and first beta build both aligned with: 19A346
If history is anything to go by (ignoring last years abnormal blip due to covid & component shortages), the new iPhones would have be having iOS 15 installed from last week of August, which was 2 weeks before the Pegasus exploit was reported to Apple. That means they would have the iOS 15 RC that we had, installed.

Now, we do know that Apple have the ability to flash update iPhones whilst boxed (so people were saying last year), so if that’s a thing, then maybe they get the new build that way, but I’ve always taken that information with a pinch of salt.
 
  • Like
Reactions: Samdh90
Why do you need to kill the profile?
Previously it gave us the option to load if we wanted as it was a newer version.
It is a bit unusual. Only Apple knows why. Maybe it’s a sign that 15.1 beta 1 comes tomorrow 🤪
 
  • Like
Reactions: dk001
Is there any reason for the average public beta tester NOT to remove beta profile at this point? Seems certain a .0.1 or .1 will be released by Friday.
I think 15.0.1 won’t have a beta. 15.1 will be the next beta and that’s the only reason you have the profile on. Would remove it now get the new build of 15.0c then put it back on.
 
  • Like
Reactions: SaguaroSeven
The latest of iOS 15 build number was 19A346 . The weather top part that show the countries name and the degree Celsius was cut off when you strolled up the app, but I have seen some still able to see the counties and degrees Celsius when stroll up, not sure why ?? Any 1 ??
 
If history is anything to go by (ignoring last years abnormal blip due to covid & component shortages), the new iPhones would have be having iOS 15 installed from last week of August, which was 2 weeks before the Pegasus exploit was reported to Apple. That means they would have the iOS 15 RC that we had, installed.

Now, we do know that Apple have the ability to flash update iPhones whilst boxed (so people were saying last year), so if that’s a thing, then maybe they get the new build that way, but I’ve always taken that information with a pinch of salt.
I get you, who knows how apple does this. I would think as soon as they ship, it's too late though. I am wondering though if Apple recompiled what we know now as the public build ahead of time for the pre-orders, then released today to everyone else. It would make sense since internally, they are way ahead but hard to say. Might have been a last minute build and restore phase as well.
 
On RC build (19A344). After deleting the Beta profile, the new update available today says

This update provides important security updates and fixes an issue where widgets may revert to their default settings after restoring from a backup.
 
Odd: still on RC. Had watchOS 8 update available (1.2GB?) when I was out and about. At home, had to free up storage to fit update and charge watch. Now for 10 min I’ve been getting “unable to check for update” cancel or try again. (Rinse, repeat)
 
Odd: still on RC. Had watchOS 8 update available (1.2GB?) when I was out and about. At home, had to free up storage to fit update and charge watch. Now for 10 min I’ve been getting “unable to check for update” cancel or try again. (Rinse, repeat)
Restart both your phone abs watch. I had that abs failed 3x. Once I restarted everything worked.
 
  • Like
Reactions: SaguaroSeven
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.