Apple Silicone "This application is not supported on this mac"

[googlechromelabs]

Apple Silicone "This application is not supported on this mac"

[thiagowfx]

Cannot reproduce (M1 Pro):

[dtoms]

Interesting, thank you. that does work when launched from the command line. It did not work for me when launched from finder. That's not really the important use case but was confusing. Is that expected?

[thiagowfx]

Also cannot reproduce, see screenshot below (you can see I don't get the overlay 🚫 icon).

I'm glad it works for you from the command-line so that it doesn't block you. Not sure why the behavior in Finder is different for both of us though.

[dtoms]

That screenshot was helpful. Here was some additional blurbs when I launched via the command line.

My arch is arm64, but the install process installed mac-115.0.5790.102/chrome-mac-x64/ whereas your screenshot shows chrome-mac-arm64...

daniel.toms@Q9JQNC9X77 ~ % arch                                         
arm64
daniel.toms@Q9JQNC9X77 ~ % npx @puppeteer/browsers install chrome@stable
[email protected] /Users/daniel.toms/chrome/mac-115.0.5790.102/chrome-mac-x64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing
daniel.toms@Q9JQNC9X77 ~ % cd  /Users/daniel.toms/chrome                
daniel.toms@Q9JQNC9X77 chrome % mac-115.0.5790.102/chrome-mac-x64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing
zsh: no such file or directory: mac-115.0.5790.102/chrome-mac-x64/Google
daniel.toms@Q9JQNC9X77 chrome % mac-115.0.5790.102/chrome-mac-x64/Google Chrome for Testing.app/Contents/MacOS/G                       
daniel.toms@Q9JQNC9X77 chrome % "mac-115.0.5790.102/chrome-mac-x64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing"
[57465:259:0723/083617.892174:ERROR:chrome_browser_main.cc(1036)] The use of Rosetta to run the x64 version of Chromium on Arm is neither tested nor maintained, and unexpected behavior will likely result. Please check that all tools that spawn Chromium are Arm-native.
[57465:259:0723/083621.062646:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.

[dtoms]

So it seems like my mac has rosetta running and the installer chooses to install a different architecture. i don't know if that's something that can/should be fixed, or perhaps, noted somewhere. or if its just my own environment problem to deal with. i would suspect others would hit this in the future though.

[mathiasbynens]

FYI @OrKoN. Is @puppeteer/browsers selecting the wrong architecture?

[OrKoN]

I am not able to reproduce:

❯ arch
arm64
❯ npx @puppeteer/browsers install chrome@stable
Downloading chrome r115.0.5790.102 - 121.5 MB [====================] 100% 0.0s
[email protected] /Users/alexrudenko/src/pptr-test/chrome/mac_arm-115.0.5790.102/chrome-mac-arm64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing

[OrKoN]

We rely on Node to detect the platform. What does node -e "console.log(require('os').arch())" return for you? It should be the same as arch.

[dtoms]

Ah, got it. We use asdf and are on an old node version 16.13.1 which does not correctly detect the arch. Switching to v20.5.0 and its correctly detected and Chrome for Testing works as expected. You might consider adding a nodejs check to the install, or a note to the FAQ, or perhaps this issue will help future travelers. Thanks all!

(not sure the closing protocol here so will leave open)

[thiagowfx]

@OrKoN Do you want to move the issue to https://github.com/puppeteer/puppeteer before we close this bug, or is would you say it is WAI?

[OrKoN]

not sure, I am unable to reproduce this behaviour:

❯ nvm exec 16.13.1 node -e 'console.log(require("os").arch())'
Running node v16.13.1 (npm v8.1.2)
arm64

I think it is WAI and we can close this bug given that node 16 is reaching EOL in September.

[dtoms]

for posterity, with asdf

daniel.toms@Q9JQNC9X77 ~ % asdf local nodejs 16.13.1
daniel.toms@Q9JQNC9X77 ~ % node -e 'console.log(require("os").arch())'                         
x64

[OrKoN]

@dtoms so this is an bug specifically with asdf? do you know if there is an open bug report?

[dtoms]

@OrKoN I don't know sorry.

[thiagowfx]

Since it's working with nvm, we can just close this. If more issues come up related to asdf then we can reconsider.