I would out £1 on it being Pegasus fix as a minimum.That is correct, a very minor revision change. The RC was 18A344
I would out £1 on it being Pegasus fix as a minimum.That is correct, a very minor revision change. The RC was 18A344
Probably right, would make no sense having 14.8 with a security fix, then release 15 without those same security fixes.I would out £1 on it being Pegasus fix as a minimum.
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.Probably right, would make no sense having 14.8 with a security fix, then release 15 without those same security fixes.
Ok, I was starting to think I was the only one. I’m hoping this isn’t still present in the release today.I’m also having this bug and reported it in feedback. Super annoying.
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: 19A346It 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.
Up to date for me on the 12. No new update.New build.
422Mb update on 12 Pro from RC
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.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 you have the beta profile installed, that is why. Remove and reboot and you’ll see it.Up to date for me on the 12. No new update.
Ah yes. Silly me. Forgot to do that. It shows up now.If you have the beta profile installed, that is why. Remove and reboot and you’ll see it.
It’s only cos 4 of the work devices weren’t showing it and I realised I hadn’t done that. Lol.Ah yes. Silly me. Forgot to do that. It shows up now.
It’s only cos 4 of the work devices weren’t showing it and I realised I hadn’t done that. Lol.
All done and really loving it on iPad. My husband was a bit angry because we were 3 for diner…the two of us and my iPad 😂How are you holding up, buddy? 😉🖐
It is a bit unusual. Only Apple knows why. Maybe it’s a sign that 15.1 beta 1 comes tomorrow 🤪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.
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.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.
All done and really loving it on iPad. My husband was a bit angry because we were 3 for diner…the two of us and my iPad 😂
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.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.
Hey mate, if you’re still having safari slowdowns, I unplugged my modem for 10 seconds and reset network settings, all good now 👌Watch Twitter go mad at iOS 15 it ruins Apple Music you can’t even go into settings lol and there won’t be a new build as we would of had rc2
This update provides important security updates and fixes an issue where widgets may revert to their default settings after restoring from a backup.
Ok, worked when started from watch.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.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)