Yeah I am done looking at the past for patterns because you can find a relevant thing for almost any day of the week outside of Friday.the last few .4 betas have been on a Thursday. probably doesn't mean anything though
Yeah I am done looking at the past for patterns because you can find a relevant thing for almost any day of the week outside of Friday.the last few .4 betas have been on a Thursday. probably doesn't mean anything though
For waiting... one more effort and for IOS 19Let's skip ahead and start to wait for beta 2
Hey maybe beta 1 that was allegedly set for the other day was such a mess that it ended up being internal testing only and we really will start with 2.Let's skip ahead and start to wait for beta 2
I don’t believe that we start with beta 2 …Hey maybe beta 1 that was allegedly set for the other day was such a mess that it ended up being internal testing only and we really will start with 2.
Agreed.For those who really thought iOS 18.4 was going to drop today… Apple pulled iOS 18.4 on Tuesday because of issues. Do you really think they would release it that fast?
I’d rather Apple fix the issue than brick my iPhone.
If it’s true Apple was having engineering issues with 18.4, which I’m inclined to believe because they have no other reason to have such a long gap in beta testing, they might just work on it through the weekend and release it on Monday instead of trying to rush it out. But who knows, we’ve all been wrong everyday the past couple weeks.
We could still have a good “full” beta cycle if it drops early next week. It could still be a fairly ambitious update. And who knows, maybe it will drop tomorrow or later today… If your theory is that they’re pushing it back due to issues, I doubt they would need to do so with a nothing burger update with nothing to go wrong like 18.3…So since we’re clearly not getting a “full” beta cycle now, I think it’s safe to say 18.4 won’t be a very ambitious update. Because a few weeks ago, people had it flipped around and thought it would be an ambitious update, and that it would need an extensive testing cycle.
On February 4, I guessed it was coming February 10, and lots of people thought that would be cutting close and wouldn’t allow for enough time. So beta 1 on Monday would be cutting an extra 2 weeks off that.We could still have a good “full” beta cycle if it drops early next week. It could still be a fairly ambitious update. And who knows, maybe it will drop tomorrow or later today… If your theory is that they’re pushing it back due to issues, I doubt they would need to do so with a nothing burger update with nothing to go wrong like 18.3…
All of us should adopt this strategy. The iOS team at Apple is probably watching this thread, enjoying some popcorn, and having a blast seeing all of us squirm. Let's not give them any more satisfaction! They'll eventually get bored and get back to work on releasing the beta.New strategy- pretend I don’t care about 18.4 so it comes faster.
It depends on how many of the betas you space two weeks apart. If only the first two betas are spaced two weeks apart, which happens often, then we could have like 6 betas until an early April release. I think the longest beta cycle we’ve ever had was 8 betas, and that was for an initial version announced at WWDC. 6 Betas is plenty for a larger iOS update. If we were down to enough time for 3-4, I might be a bit more worried, but I think we could still see a fairly substantial update. Why else would they be running into issues and delaying? If it were a very small update with no changes like 18.3, then I wouldn’t expect there would be that many issues that would cause it to be pushed back.On February 4, I guessed it was coming February 10, and lots of people thought that would be cutting close and wouldn’t allow for enough time. So beta 1 on Monday would be cutting an extra 2 weeks off that.
I agree with the bolded, I think new features have caused 18.4 to be pushed back. But that could mean that they’re pushing those features back to 18.5 and they’re rewriting 18.4.It depends on how many of the betas you space two weeks apart. If only the first two betas are spaced two weeks apart, which happens often, then we could have like 6 betas until an early April release. I think the longest beta cycle we’ve ever had was 8 betas, and that was for an initial version announced at WWDC. 6 Betas is plenty for a larger iOS update. If we were down to enough time for 3-4, I might be a bit more worried, but I think we could still see a fairly substantial update. Why else would they be running into issues and delaying? If it were a very small update with no changes like 18.3, then I wouldn’t expect there would be that many issues that would cause it to be pushed back.
Can you post a link please?iOS 18.4 beta 1 (22E5200m)
iOS 18.4 beta 1 (22E5200t)
iOS 18.4 beta 1 (22E5200u)
Build numbers being reported on X tonight.
Honestly, it doesn’t bother me too much. People are excited, I get it, I don’t like to rain on anyone’s parade by replying directly. But it’s funny, when I post my own more reserved, slightly more pessimistic predictions, the first stage of grief kicks in with some people lol.All of us should adopt this strategy. The iOS team at Apple is probably watching this thread, enjoying some popcorn, and having a blast seeing all of us squirm. Let's not give them any more satisfaction! They'll eventually get bored and get back to work on releasing the beta.
The past ~52 pages (~1300 posts) of repeating the same thing over and over is a bit wild. Are we in Groundhog Day?
Rewriting 18.4? We’ve seen them simply remove features from versions of iOS before during a beta cycle, I don’t think it would require a complete rewrite in order to remove some features not yet ready for testing. Maybe I’m wrong, but I think it’s more likely that if there’s been a delay, it would be because they’d be trying to fix broken features before releasing to testers, not due to removing them. One would think that rolling back broken features would be fairly straightforward, and wouldn’t require weeks of work to do when they’ve done it mid-beta cycle in the past.I agree with the bolded, I think new features have caused 18.4 to be pushed back. But that could mean that they’re pushing those features back to 18.5 and they’re rewriting 18.4.
I mean, either way, I doubt Apple planned on sitting on 18.4 for a full month after releasing a minor 18.3 update to the public. Something went awry IMO.
So does that mean it might be coming later today? Like a rare 4PM release?iOS 18.4 beta 1 (22E5200m)
iOS 18.4 beta 1 (22E5200t)
iOS 18.4 beta 1 (22E5200u)
Build numbers being reported on X tonight.
Well it depends. I’m not a developer, but I know that removing a feature isn’t as simple as removing a few lines of code. Now, some would be easier to remove than others. It depends on how interconnected that new feature was to the rest of the system. Screen monitoring, in-app actions, and personal context are very interconnected to every facet of the system I would imagine.Rewriting 18.4? We’ve seen them simply remove features from versions of iOS before during a beta cycle, I don’t think it would require a complete rewrite in order to remove some features not yet ready for testing. Maybe I’m wrong, but I think it’s more likely that if there’s been a delay, it would be because they’d be trying to fix broken features before releasing to testers, not due to removing them. One would think that rolling back broken features would be fairly straightforward, and wouldn’t require weeks of work to do when they’ve done it mid-beta cycle in the past.
It’s a private account sadly, but I believe it’s the same account MacRumors post articles about and don’t name the user.Can you post a link please?
Interesting that the same b1 has different build numbers for 3 of them. I imagine one of them is for the 16e since it has a different build number for 18.3.1. But what about the third? Interesting.It’s a private account sadly, but I believe it’s the same account MacRumors post articles about and don’t name the user.
Interestingly this account posted the build number for 18.3.1 mere minutes before it was released so can’t rule out a drop later today.
Sure, it’s not just removing some lines of code, but it is actually pretty close to that as I understand it. If the Siri on-screen awareness is going to work the way I’m thinking, it should be basically a model connected with Siri that analyzes screen recordings delivered to it by the system. This wouldn’t have direct integration into apps or anything like that, it would mostly be an AI model added onto Siri, meaning it should be fairly straightforward to roll back and just stick with the existing Siri setup, and it wouldn’t impact the rest of the system. And Apple is still going to need to support standard Siri on older iPhones anyways, so it’s not like they would even have to completely redo everything, just roll back the stuff for the new Siri features on newer phones. That’s at least the way I understand it, so if that’s correct, then I don’t think doing so would take several weeks to do.Well it depends. I’m not a developer, but I know that removing a feature isn’t as simple as removing a few lines of code. Now, some would be easier to remove than others. It depends on how interconnected that new feature was to the rest of the system. Screen monitoring, in-app actions, and personal context are very interconnected to every facet of the system I would imagine.