You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GUI (Graphical User Interface), CLI (Command-Line Interface)
Platform
OSX
Export format
No response
Steps to reproduce
Explained below
Details
If you try to run the app after downloading, it won't launch due to macOS's security policies. You need to manually bypass the app signing check to work around this issue: #1234 (reply in thread)
Packaging the app as .app bundle may help resolve this issue. Ideally, we'd want to integrate the bundling stage in the existing CI process.
Checklist
I have looked through existing issues to make sure that this bug has not been reported before
I have provided a descriptive title for this issue
I have made sure that this bug is reproducible on the latest version of the application
I have provided all the information needed to reproduce this bug as efficiently as possible
I have sponsored this project
I have not read any of the above and just checked all the boxes to submit the issue
The text was updated successfully, but these errors were encountered:
Commenting from the other thread, since I brought up the app bundle.
If you have an unsigned bundle, it is treated similarly to how Windows treats an unsigned .exe file. You have to right click -> open the first time in order to confirm that you want to run unsigned code, but after that it remembers the app and won't prompt you again.
I haven't done mac app stuff in a while, but iirc there's nothing magic about what xcode does when making a .app bundle. You just need the correct layout and an info.plist file that tells the OS how to set up the runtime.
Version
v2.43.3
Flavor
GUI (Graphical User Interface), CLI (Command-Line Interface)
Platform
OSX
Export format
No response
Steps to reproduce
Explained below
Details
If you try to run the app after downloading, it won't launch due to macOS's security policies. You need to manually bypass the app signing check to work around this issue: #1234 (reply in thread)
Packaging the app as
.app
bundle may help resolve this issue. Ideally, we'd want to integrate the bundling stage in the existing CI process.Checklist
The text was updated successfully, but these errors were encountered: