How to distribute Chromium on arm Macs

[Obaid Ur Rehman]

I have made some changes in Chromium and now want to distribute it to my user base. The issue is when someone downloads it and tries to install it on their arm Mac(M1 and M2 chips based), due to the com.apple.quarantine bit set by the browser, it gives the error  "Chromium" is damaged and can't be opened. You should move it to the Trash." I know this could be fixed using xattr command but is there any workaround to this as fixing it individually is not a solution and possible.

Thanks

[Ken Russell]

These instructions describe how to get past the quarantine bit issue:

https://chromium.googlesource.com/chromium/src.git/+/main/docs/mac_arm64.md

On Thu, Oct 13, 2022 at 5:31 PM Obaid Ur Rehman <obaid...@gmail.com> wrote:

I have made some changes in Chromium and now want to distribute it to my user base. The issue is when someone downloads it and tries to install it on their arm Mac(M1 and M2 chips based), due to the com.apple.quarantine bit set by the browser, it gives the error  "Chromium" is damaged and can't be opened. You should move it to the Trash." I know this could be fixed using xattr command but is there any workaround to this as fixing it individually is not a solution and possible.

Thanks

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/4b50132e-48c5-40e8-95fa-042d0dfe3d1bn%40chromium.org.

[Dirk Pranke]

Doesn't the solution on that page mean everyone who would download the zip file would have to remove the quarantine bit themselves? I think that's what Obaid is trying to avoid.

That said, I don't know if there is a solution to this problem.

-- Dirk

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAMYvS2fti8dY3pKpjz5Q39cogY8HR84oyQWM%2BBV-GSgHqO1uOw%40mail.gmail.com.

[Robert Sesek]

Mac apps need to be code signed and notarized before distribution. Chrome uses the script documented here to produce its signed and notarized builds.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAEoffTDYUNWv0gfowe%2BiodHb53rjnnr2z%3DiYdz%3DPGADyaEQtgA%40mail.gmail.com.