-
Notifications
You must be signed in to change notification settings - Fork 41
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
changing settings after creation in 3.0 results in signature error #120
Comments
Came to open an issue for the same thing I think.
|
@danieltomasz thanks for the report! It sounds like you’re running into https://developer.apple.com/library/archive/qa/qa1940/_index.html If you’re open to it, it would be helpful if you could try the two commands mentioned on that page and report back:
|
I installed multi v3 as Multi3 now, so probably I to messed with paths to run
Suprisingle the multi from homebrew gives similar results (earlier Multi v3 was installed as Multi and then I reinstalled Multi v2 as Multi)
point both to Multi and Multi3 give me similar results with addition to other flags properties that are ok |
I am MacOS 13.4.1 |
After update of homebrew version to 3.0.0 I am trying with other sites and I cannot reproduce error so I am closing this issue |
Thanks for following up! It’s interesting to know that mixing a homebrew installation with a manual one causes issues. Glad you got it working. |
I tried to edit settings that I set previously with
The installation from scratch went without error It seems that trying to change anything in the settings, is changing the signature, does the 2.4 has different mechanism for storing settings? In recent MacOS releases there were some changes related to signing the apps I think |
Happening to me as well, I am running Ventura! |
When I created my app with multi 2.2.3 downloaded from homebrew those settings worked
When I updated to multi 3.0 when I try to save it I am getting error
the app is created but is broken, downgrading to 2.2.3 I able to create app again
the settings are taken from readme
The text was updated successfully, but these errors were encountered: