Repository navigation
[BUG]: Dev Proxy fails to start on macOS 27 with "bad CPU type in executable" #1914
Description
Activity
Can't repro. Works just fine on my M2 MBAir and M5 MBP, both on macOS 27. Can you tell more about the device you've been seeing this on?
I can repro it when installing from homebrew. It seems to be related to requiring Rosetta since we only publish osx-x64 binaries. Researching if we could publish a working osx-arm64 binary without having an Apple developer account.
Fixed in latest beta by adding an osx-amd64 release
- linked a pull request that will close this issueAdd osx-arm64 release build #1916
on Oct 9, 2026
Description
After upgrading to macOS 27, running Dev Proxy from zsh fails immediately with a CPU architecture compatibility error.
Expected behaviour
Running
devproxyshould start Dev Proxy normally on macOS 27.Actual behaviour
The command exits immediately with:
Steps to reproduce
devproxy.bad CPU type in executable.Dev Proxy Version
Unknown.
devproxy --versioncannot run because the same executable compatibility error prevents Dev Proxy from starting.Operating system (environment)
macOS
Shell
zsh
Configuration file
N/A. The failure occurs before Dev Proxy starts or loads a configuration file.
Additional Info
This started after upgrading to macOS 27. The error suggests that the installed Dev Proxy binary or its launcher may not contain an architecture compatible with the current macOS environment.