As this open-source project currently doesn't provide code signing for all platforms and only uses GitHub Actions for simple build releases, you might encounter some of the issues mentioned above. This issue collects related problems and provides temporary solutions.
macOS warning about being damaged: Currently, it uses "signingIdentity": "-" to bypass signing. You need to go to "Security & Privacy" in macOS settings and choose "Open Anyway."
macOS not working after updates: I suspect this might be due to the inconsistency in code signing with each new build version. You may need to remove and re-add (input monitoring) permissions after each update.
Windows warning about malware: I haven't encountered this issue on Win11 Pro, but some versions of Windows (or certain security software) might show this alert. You can choose to ignore it.
As this open-source project currently doesn't provide code signing for all platforms and only uses GitHub Actions for simple build releases, you might encounter some of the issues mentioned above. This issue collects related problems and provides temporary solutions.
macOS warning about being damaged: Currently, it uses
"signingIdentity": "-"to bypass signing. You need to go to "Security & Privacy" in macOS settings and choose "Open Anyway."macOS not working after updates: I suspect this might be due to the inconsistency in code signing with each new build version. You may need to remove and re-add (input monitoring) permissions after each update.
Windows warning about malware: I haven't encountered this issue on Win11 Pro, but some versions of Windows (or certain security software) might show this alert. You can choose to ignore it.