-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Override of syncthing
Executable from .app to custom filesystem path via NSUserDefaults resets always back to bundle path
#212
Comments
syncthing
Executable?syncthing
Executable?
…nly when non-exisiting. See issue #212
See my commit above in the issue branch. I think it was because it was always set, instead try load. Then set when empty. It is untested, currently I have no environment to build dmg setup on my system. And the continuous integration with github actions doesn't create DMG in debug mode. Have a look. |
Looks like that will work! I can't test right at this moment but will try ASAP. In the meantime, I found that stripping |
syncthing
Executable?syncthing
Executable from .app to custom filesystem path via NSUserDefaults resets always back to bundle path
@xor-gate I will test by tomorrow, thank you for the build. |
@xor-gate LGTM ! 👍 |
Great, this was modified without testing. But it was an easy fix :-) |
😱 |
It would be nice to have it also in the documentation README for power users. |
I've been running a custom compiled
syncthing
binary until syncthing/syncthing#9430 is pulled into a release.Today I replaced my macOS bundle with v1.27.4, and could no longer run the app due to Gatekeeper. Ugh.
I saw in the NSPrefs that there is a key to specify the Executable:
But trying to set it:
I found it immediately reverts back to the default one. Seems due to this code:
syncthing-macos/syncthing/STApplication.m
Lines 72 to 77 in 43c7282
Is there an env var or any other supported way to override the default syncthing binary with the app bundle?
related:
The text was updated successfully, but these errors were encountered: