Universal BuildsĪ “universal” (or “fat”). A small number of swarming bots are also available for Googlers to run tests on.Īrm Mac-specific bugs are tagged with the Mac-ARM64 label.

To fix this, open a terminal and run % cd ~/Downloads & xattr -rc Chromium.appĪs an alternative to building locally, changes can be submitted to the opt-in mac12-arm64-rel trybot. In Console.app, the kernel will log kernel: Security policy would not allow process: 2204, /Users/you/Downloads/Chromium.app/Contents/MacOS/Chromium and amfid will log amfid: /Users/you/Downloads/Chromium.app/Contents/MacOS/Chromium signature not valid: -67050. If you zip, upload Chromium.app to some web service and download it to an Arm Mac, browsers will set the bit, which will cause the Finder to say 'Chromium' is damanged and can't be opened. If you copy it using macOS’s “Shared Folder” feature and Finder, Chromium.app should be directly runnable. a regular is_debug=false build), you can just copy over Chromium.app from your build directory.

If you are on an Arm Mac, your build will by default be an Arm build, though please see the section below about building on Arm Macs for specific things to keep in mind.Ī note about copying a Chromium build to your Arm Mac. If you are on an Intel Mac, all that's required to build Chromium for arm64 is to add a target_cpu = 'arm64' line to your args.gn. The tester bots don’t have Rosetta installed.ĪSan builds do not yet work ( tracking bug) Building for Arm Macs There‘s also a tester bot that continuously runs tests. This bot does not have Rosetta installed. There's a main waterfall bot that builds for Arm on an Arm bot as well. There's a main waterfall bot that builds for Arm. The short summary is that almost everything works, without needing Rosetta. This document describes the state of Chromium on Apple Silicon Macs.

Mac chromium