Closed BornInWeb closed 2 years ago
Thank you @BornInWeb! I can reproduce the issue with Build Revision 1020539. As this web app only links to pre-built binaries, I'll ping the appropriate folks to let them know so that they can fix it.
FYI The build was downloaded from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac_Arm/1020539/
I just tried a whole bunch of Mac_Arm binaries from commondatastore all the way back to May but none worked. Are so few people downloading Chromium binaries that no one noticed this until now? Also why was this issue closed?
STOP spam !!!
Le 6 juil. 2022 à 02:36, Simon Ramstedt @.***> a écrit :
I just tried a whole bunch of Mac_Arm binaries from commondatastore all the way back to May but none worked. Are so few people downloading Chromium binaries that no one noticed this until now? Also why was this issue closed?
— Reply to this email directly, view it on GitHub https://github.com/beaufortfrancois/download-chromium/issues/75#issuecomment-1175632675, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ7R6EQ2ZZ56JK5D4ZXH2HTVSTIHNANCNFSM52OK5QTA. You are receiving this because you were mentioned.
These are genuine questions. I'm not super familiar with Chromium but interested in how it's built and distributed so I was hoping @beaufortfrancois would be able to shed some light on why all these Mac binaries are faulty. E.g. maybe they used to work but a MacOS update broke them.
The second question "why was this issue closed?" is genuine too. The current binary still doesn't work (on my M1 Macbook Air at least) so the issue doesn't seem be resolved and others might find the information in here useful
I've found the root cause. According to https://chromium.googlesource.com/chromium/src/+/main/docs/mac_arm64.md#building-for-arm-macs,
If you zip, upload Chromium.app to some web service and download it to an Arm Mac, browsers will set the
com.apple.quarantine bit
, which will cause the Finder to say"Chromium is damaged and can't be opened. You should move it to the Trash."
... To fix this, open a terminal and run% cd ~/Downloads && xattr -rc Chromium.app
I've tried this and it works great. I'm talking to the chrome team to see if there's something to improve the current situation.
As a reminder, https://download-chromium.appspot.com/ is a simple tool that points to existing Chromium builds.
Ah perfect, thank you! Maybe it's because the binaries weren't signed (properly)?
Indeed. Here's the official chromium bug with all details: https://bugs.chromium.org/p/chromium/issues/detail?id=1231936
Build Revision: 1020327