-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signing issues on M1 macs #123
Comments
@hjaltisan Did you manage to get this to work for your M1 mac without the entitlements? |
@mbforbes No I did not. Haven't tried again recently though. |
@hjaltisan Did your steam overly work on Mac M1 though? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey. Similar to #111 I'm having issues that result in
Error: failed to init the steamworks API
My setup:
The issue:
I took the example folder from this repository and created my own repository that does pretty much the same, but via electron-forge. This repository can be found here: https://github.com/hjaltisan/shiny-doodle
I can run
npm run start
and if I'm running via Steam, after a couple of seconds I will see my username on the screen.If I however run
npm run package
it will instead show me the aforementioned error.Here is the thing though. I'm running this on M1 mac. If I build with
npm run package -- --arch=universal
to build an app that works both onarm
andx64
it will still fail on my M1, but it will work onx64
!The only difference between the
npm run start
andpackage
are that inpackage
I'm also signing everything.So the signing works perfectly for
x64
macs, but doesn't forM1
!The only way I've found so far for it to work on
M1
is by disabling library validation, as I'm doing on this branch (https://github.com/hjaltisan/shiny-doodle/tree/entitlements) but I'd rather not have to add that entitlement.The text was updated successfully, but these errors were encountered: