Closed id3v1669 closed 1 year ago
Sounds like a duplicate of https://github.com/SpacingBat3/WebCord/issues/173.
I'll close it for that reason, although this issue states this problem affects also universal
binaries (I guess maybe I need to update the issue title?).
As of the state of this issue in general, it probably won't be fixed unless I will decide to buy a certificate. Until then, both Windows and MacOS will not trust WebCord binaries at all as they will stay unsigned.
Sounds like a duplicate of #173.
I'll close it for that reason, although this issue states this problem affects also
universal
binaries (I guess maybe I need to update the issue title?).As of the state of this issue in general, it probably won't be fixed unless I will decide to buy a certificate. Until then, both Windows and MacOS will not trust WebCord binaries at all as they will stay unsigned.
Wrote this report exactly because of universal version and because there found the solution how to hot fix this. May be until you buy a certificate add .command script that performs actions that I wrote in this report into dmg?(as hot fix) sign_webcord.command.zip
Aknowledgements
master
branch.*Environment
Describe the problem
dmg versions for arm and universal webcord crash and do not work.(x64 works) If I build package on target machine, it creates dmg but still does not work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
App starts without crash
Additional context
so the problem is with signing launch file for arm and universal versions
Workarounds
Signing webcord launch file(webcord.app/Contents/MacOS/webcord) with command " codesign -f -s - --deep "$FILEPATH" " and allowing it to bypass gatekeeper by command " xattr -rd com.apple.quarantine "$FILEPATH" "
or use prepared script GateKeeper-Helper (func 3 and 4)