[bug] The build results on the Mac platform are confusing. The aarch64.dmg file cannot be launched on Macs with Intel, M1, and M2 chips, while the x64.dmg file can be successfully launched on Intel, M1, and M2.
heneyin opened this issue · comments
The build results on the Mac platform are confusing. The aarch64.dmg file cannot be launched on Macs with Intel, M1, and M2 chips, while the x64.dmg file can be successfully launched on Intel, M1, and M2.
According to the official documentation, aarch64 is intended for Apple chips, while x64 is meant for Intel chips. However, the actual results are contrary to this description, which is quite confusing. I am unsure whether this discrepancy is due to a bug in tauri-action or if I am using it incorrectly.
My test demo：https://github.com/heneyin/tauri-demo/releases/tag/v0.0.0
Thanks
im having the same issue. the arch build shows as corrupted whereas the x86 version loads fine. im on a M2 macbook.
macos is simply stricter about arm apps and now requires it to be signed. Until Apple fixes this, you can make it behave like x86 apps by signing it with an empty certificate, to do this, add "signingIdentity": "-" to your tauri.conf.json file (inside tauri.bundle.macOS.
why is this closed? currently the docs suggest you can use this and it doesn't work..
shouldnt the docs be updated?
I closed it because it's not a tauri-action specific problem, if you build on a local macos system and then try it on another it will have the same issue.
It's kinda tracked here tauri-apps/tauri#8763 and also on the radar for the v2 docs.