Aren’t the first two PBs a week after the devs before they switched to the next day?
Last year and the year before, the 2nd PB was released the day after the corresponding DP.
Aren’t the first two PBs a week after the devs before they switched to the next day?
Aren’t the first two PBs a week after the devs before they switched to the next day?
No 17 apps before the public release.What would be the actual point of holding a perfectly useable beta from the public for another week? So far the feedback on PB2 sounds better than that of PB1. Besides, the more beta testers they get on board, the more issues could be flagged out, so it is a win-win. The only possible reason to hold it off from the general public I can think of would be allowing 3rd party app developers to update their apps, if needed? But then again, can they even push these updates out at the App Store before the official iOS 17 is out?
Guess I haven’t been paying attention. Always remember them as weeklies for the first two PBs.Last year and the year before, the 2nd PB was released the day after the corresponding DP.
What would be the actual point of holding a perfectly useable beta from the public for another week? So far the feedback on PB2 sounds better than that of PB1. Besides, the more beta testers they get on board, the more issues could be flagged out, so it is a win-win. The only possible reason to hold it off from the general public I can think of would be allowing 3rd party app developers to update their apps, if needed? But then again, can they even push these updates out at the App Store before the official iOS 17 is out?
Apple releases these betas on a schedule. Not based on “feedback”.
And no, third party developers cannot update their apps (for external distribution) until the RC.
In the context of PB seeds there is no schedule. If DB4 is not good, then they can skip its PB seed. In the past they have skipped PB seeds on occasion.Apple releases these betas on a schedule. Not based on “feedback”.
And no, third party developers cannot update their apps (for external distribution) until the RC.
Then I still do not understand the purpose of a longer gap between developer and public beta releases.
I get it that developers have a priority, but does it really matter for Apple if they release the same PB build as the DB a few hours, a day or a week later?
In the context of PB seeds there is no schedule. If DB4 is not good, then they can skip its PB seed.
Generally, the Developer Betas get installed on a much smaller set of devices overall than the Public Betas do. There's been times in the past where there's been "show stopper" type of bugs that delayed the PB release..Then I still do not understand the purpose of a longer gap between developer and public beta releases.
I get it that developers have a priority, but does it really matter for Apple if they release the same PB build as the DB a few hours, a day or a week later? I just can’t see the logic behind this delay. 🤷🏻♂️
Anyone involved with PB releases since they restarted, will remember at times there was no PB release on occasion associated with a dev release. It's like they skipped that time, and it showed up with the next dev seed. I wouldn't say it occurred that often, sometimes.To my knowledge, they have never “skipped” a PB, however.
I guess could be slightly delayed because of macOS.Damn. Was hoping for the Public beta today
Generally, the Developer Betas get installed on a much smaller set of devices overall than the Public Betas do. There's been times in the past where there's been "show stopper" type of bugs that delayed the PB release..
*Consider the Dev Beta Seed to be the guinea pigs for the Public Beta Seed ;-)
Understood, yet I thought that the general feedback from DB4 was better than DB3?
Guessing more skin shades and genders of emojis
More bloat ware to get you to get a new phone
More creepy photo scanning type stuff
More space used by the OS, again to get you to buy a new phone
Maybe now move the address bar in safari to the side
Who do they get to test these things out? Is it just freaks from SFO and Portland, or do they want working blue collar types opinions too, end of the day there are more of us.
I remember one of my buddies was over, his phone said he needed to “upgrade” looks at it, laughs and shows me, was like to get more dumb emojis and some other pointless stuff, we both laughed
I’d rather have zero emojis and have the software not creep in my personal photos, as would most of the country
I’d rather not have the address bar on the bottom, but have a extra Gb of space on my phone
Rather not have a translucent Lock Screen thing , but have my device run faster or get better battery life
Well how about trying an Android?
Not really surprised, usually for Bi-weekly betas, PB comes after a week. For weekly betas, PB comes a few hours/a day afterwards.
I still believe Public Beta is coming tomorrow. Today was Samsung Day. So, Apple took a break today.
Not really surprised, usually for Bi-weekly betas, PB comes after a week. For weekly betas, PB comes a few hours/a day afterwards.
Not saying Apple can't release an updated PB this week, but not surprised if not as it happened before.
First of all there is no indication that Apple bases the date of any release - developer or public - on publicly available (i.e. social media, tech journalists, pundits) information. As I said earlier today, all you see in these forums is the “bad”. And the “bad” might impact 1/100 of 1% of users. Apple can’t take what is posted here and make any meaningful decisions.
Apple relies on hard data. Data it gets via Feedback submissions and data it gets via the logging and diagnostics that devices running the betas are sending to Apple all the time.
And even that data doesn’t appear to affect the schedule of releases.
The one thing that does appear to affect the schedule of releases is the discovery of so-called “zero day” exploits: malware that can lead to significant problems without any need for further exploitation. Those get Apple’s (and Google’s and Microsoft’s) immediate attention and have appeared to impact release schedules in the last few months.
Apple has a schedule to keep: the OS must be ready in time to install on new iPhones as they start coming off the line in late August or early September. Nothing can impact that production run. If it does, heads roll. And the stock price craters.
That’s not going to happen.
Less changes the later they get in the beta period so less chance of changes that could/would brick devices.I understand that Apple do not base their beta release schedule on these forums and the dangers of “zero day” exploits.
So if we take all this into consideration, that Apple may want to “overprotect” the general public more than devs, even though not many regulars will go into betas, then the question remains - why does this DB-PB release gap varies from 1 week early in the beta cycle and then drops to just 1 day and 1 hour apart closer to the final release.
Do Apple just get more confident with less probability of “zero day” exploits at that point?