Apple Seeds Third Beta of macOS Tahoe to Developers

[StephN999]

Weird, this caused the installer to run, but it fails during installation.

For me too, I've spoken too soon... 😕

 

[lonewolf12016]

For me too, I've spoken too soon... 😕

Yeah I spoke to soon as well, as the installer fails as well

 

[elvisimprsntr]

I canvassed my apps and still have a bunch that are Intel. The most critical is TurboTax. I’ll wait it out for Apple to fix the issue.

 

[Templeton]

I believe I found the issue with macOS distribution. It looks like Apple ran into an issue affecting the Apple Silicon version of macOS Tahoe beta 3. As of now, the update seem to be available only to Intel Macs.

 

[Stevez67]

Saw the information about Rosetta preventing download and installation of B3. Searched and found 3 files that include "Rosetta" in Adobe Creative Cloud. I'll check for the download again tomorrow morning.

 

[Templeton]

Still no update here in Illinois but that's because of governor probably has a tax on beta updates now.

Apple ran into an issue with Apple Silicon version. For now, the update seems to be available only to Intel Macs.

 

[Ethrem]

Apple ran into an issue with Apple Silicon version. For now, the update seems to be available only to Intel Macs.

Obvious bot is obvious.

 

[jeremz1ne]

For me too, I've spoken too soon... 😕

Same here maybe tomorrow lol

 

[ultratiem]

It doesn't seem that easy to remove Rosetta.

It is not and cannot be added later because it breaks system protection hash. You have to completely reinstall macOS. Just wait for Apple to fix and release.

 

[Microtard64]

Weird, this caused the installer to run, but it fails during installation.

I get the same result. The full installer errors out while preparing the package.

 

[thefredelement]

I get that part, but the OS is still dropping for Intel Macs, also if you sunset rosetta, surely that will create a major issue with apps that are no longer updated but still work or being used by people.


I am sure when they make the apps in Xcode they choose what they are aiming for it to run on, hence why we have apps that are designed for silicone, sites will even tell you if they run on intel or silicon chips.

So I am not sure the primary goal fits, "to test out the api" as the app thats designed to silicon wouldn't use rosetta but the new api anyways.

Personally think its a oversight on their part, hence why they pulled the update for silicon Macs, but we wont truly know considering how tightlipped Apple is.

They need to be careful with how they sunset Rosetta when there are such a large library that still depend on it.
I bet many devs wouldn't be happy for it to be wiped out even on their tests benches, bet there are some apps they use that are reliant on it still, either because "it just works" or dev behind it hasn't made a silicon version, either becasue why when it runs fine as is, or lazy to move it over.

This bug with beta 3 is probably an isolated incident, I'm sure they'll announced when they're dropping rosetta with more lead time and not just do it in a dev preview iteration. I didn't watch the platform state of the union this year but a quick search will reveal Mac OS 27 will probably be the last one with Rosetta.

As for to test out the APIs - that's exactly what this release is for, to run your current apps on it to see if any existing APIs change behavior and to use the new ones available on Mac OS 26 and to update as needed. Engineers doing that are most likely updated to run native on Apple's chips (if you build in Xcode it's ridiculously easy, depending on project complexity and dependencies).

It's 100% not for general consumers to put on production / daily machines, for issues just like this.

All that being said Apple silicon was released almost 5 years ago, which I think is starting to match the time frame of when the first Rosetta was retired for the PowerPC / Intel transition.

That's even more reason to make sure it's working in the dev beta now so that devs can port and test their apps vs the latest version of macOS.

That's been available since Big Sur for Intel apps wanting to recompile to Apple chips.

 

[anonymous6669]

Not available yet here in Toronto (Canada) it’s almost 8PM and I’ve tried multiple troubleshooting steps to get it

 

[nicolas17]

why we have to get this info here anyway. why can’t apple just tell us instead of making us find out for ourselves

as-clear-as-mud communication style of apple is infuriating and has been for decades

Everything suggests Apple still has no clue what the problem is, or they would have fixed it by now, lol

 

[dwaite]

I just got told the issue is partially fixed, but updates will still fail if you aren't in the US and in a state ending with a vowel.

 

[mikamika83]

Is that true? Can someone confirm?

 

[nicolas17]

Is that true?

Of course not.

 

[mikamika83]

Of course not.

not sure where i was supposed to see an obvious sign of that being false.
As a developer myself, i can see this being valid A/B testing strategy

 

[dwaite]

Is that true? I asked chatGPT to generate a list. Can someone confirm from the green states?

Was debating instead saying that due to a network issue it is only available over IPv4, and all four components of the address must be prime.

 

[mikamika83]

Was debating instead saying that due to a network issue it is only available over IPv4, and all four components of the address must be prime.

the fact that I would still double check my IP address tells me i gotta find something better to do with my life than being in this thread lol

 

[AndoAU]

Nothing yet in the Sea of Tranquility on the moon.

 

[tywebb13]

where is it located?

/Library/Apple/usr/share/rosetta
/Library/Apple/usr/libexec

 

[Martyimac]

My M4 iMac running the previous developer, beta, 2, is showing as 25A5295e, which should mean the next beta, for me, should end in d. Right?

 

[antmarobel]

Nothing in Brasilia...

 

[tywebb13]

My M4 iMac running the previous developer, beta, 2, is showing as 25A55295e, which should mean the next beta, for me, should end in d. Right?

build is 25A5306g for beta 3 so it would be a g

also isn’t beta 2 25A5295e not 25A55295e

looks like u got a extra 5 there

 

[mosflix]

My M4 iMac running the previous developer, beta, 2, is showing as 25A55295e, which should mean the next beta, for me, should end in d. Right?

softwareupdate --list-full-installer

run that command in your terminal and it will show you the build numbers based on what yours shows, it's 26 beta 2