There is still a significantly more than half of Julis, but there is still no sign of a public beta version of Apple’s new operating systems. It may be the case this Tuesday or tomorrow Wednesday. At least the information of an “anonymous leaker with a proven track record” suggests how Macrumors writes. Accordingly, the fourth developer betas could appear on Tuesday, then tomorrow Public betas. Alternatively, a simultaneous release would be possible on Tuesday – but only in the evening that we would type to 7 p.m.
Build numbers are already available
Apple will therefore present Build 23a5297i from iOS 26 and Ipados 26, Build 25a5316i by MacOS 26, Build 23J5316G from TVOS 26 and HomePod Software 26 as well as the Builds 23R5317G and 23M5300G from Watchos 26 and Visionos 26.
These could then also represent the public beta, with the exception of Visionos 26, for which there will apparently have no public beta phase. Beta 4 is likely to be more stable than the current Beta 3 – Apple traditionally always tests several releases with developers before the public beta starts. That also makes sense.
Beta briefly fled and captured again
Interestingly, MacOS 26 alias Tahoe was already available as a public beta on Monday evening. They saw users whose Apple account is unlocked for betas in certain circumstances Also under MacOS 15 Sequoia. Only Apple-Silicon-Macs were affected, on which the Intel emulation layer Rosetta 2 was not yet installed. If Rosetta 2 is on the Mac, the beta does not come either. The build was that from the leak, namely 25a5316i. According to Macrumors, the Beta is said to be called “MacOS26publicbeta1” in Apple’s backend.
There are said to have been users who actually wanted to install the release candidate from MacOS 15.6, which was also released on Monday evening – and instead brought Tahoe on their Mac. Apple reacted relatively quickly and pulled the public beta of MacOS 26 apparently too early. Users who want the middle to remember that public betas are not suitable for productive operation. So you should only use them on test devices and if possible not with real data (including iCloud) to rule out problems.
Discover more from Apple News
Subscribe to get the latest posts sent to your email.