steamworks.js icon indicating copy to clipboard operation
steamworks.js copied to clipboard

Signing issues on M1 macs

Open hjaltisan opened this issue 2 years ago • 3 comments

Hey. Similar to #111 I'm having issues that result in Error: failed to init the steamworks API

My setup:

  • Electron (built with Electron-Forge)
  • steamworks.js 0.3.1
  • M1 mac and x64 mac

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 on arm and x64 it will still fail on my M1, but it will work on x64! The only difference between the npm run start and package are that in package I'm also signing everything. So the signing works perfectly for x64 macs, but doesn't for M1! 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.

hjaltisan avatar Nov 17 '23 10:11 hjaltisan

@hjaltisan Did you manage to get this to work for your M1 mac without the entitlements?

mbforbes avatar Jul 29 '24 20:07 mbforbes

@mbforbes No I did not. Haven't tried again recently though.

hjaltisan avatar Aug 09 '24 11:08 hjaltisan

@hjaltisan Did your steam overly work on Mac M1 though?

gfordinal avatar Aug 21 '24 08:08 gfordinal