-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Issue with new v1.6.1-1 prerelease #111
Comments
I tried to reinstall the old https://github.com/syncthing/syncthing-macos/releases/tag/v1.0.0-2 release and it works fine without this error. |
Apple made notarization mandatory since the last release and a quick search/look didn't turn anything up that looks like doing notarization in syncthing-macos (aka searching for |
It's a conundrum. Like many things in the Apple build ecosystem it's not trivial to automate. I have a script I run manually (when I remember, which I didn't for 1.4.2) to notarize the regular Syncthing binary after we release it. |
And even then there's nonsense like this
every time, even though I just signed the new contracts, and there are new contracts every few weeks 😬 |
Oohw boy, you dance with the devil. |
Oh, the best thing is that when the notarization upload actually works, the tool just thanks you for the upload. Then at some later point you get the success/failure of the notarization process in an email. Excellent for integrating into a build pipeline. |
In this case, specifically,
Ah. "Package Invalid". I see. 😠 |
I think that means we need a newer Go (1.14). Whether you then also need to do some magic here I don’t know. |
Can we try to compile 1.5.0 syncthing with a correctly signed cert and see if we can get it working? When the release is ready of course. |
Now v1.5.0 is released can you have a look to upgrade to go 1.14 for macOS ? I still get the same error but then with the latest v1.5.0 so i'm unable to resolve #113. |
Go 1.14 didn't change this situation, at least not by itself. I'm upgrading the builder to catalina and newer xcode to see what happens. |
Go itself should be "compatible" since 1.13.5: golang/go#35748 |
Yeah so we're hitting something else then, maybe our linker flags or some other oddness.
(Go 1.14.2) |
Figured it out, it needs to be enabled at code signing time as well. So 1.6.0-rc.1 and newer will be notarized. |
So Syncthing itself is now notarized, so I expect this is fine? It should be possible to do a release with an updated binary? |
I fixed the DMG build for Catalina, but the app doesn't notarize very well regardless: https://osxapps-ssl.itunes.apple.com/itunes-assets/Enigma123/v4/29/34/a5/2934a52d-e1f1-8589-b460-ae93de075f9c/developer_log.json?accessKey=1591361341_1785601510916194979_dQSsDjOSH3ciNP%2BFdg0CJ0CtJeH2LB3X%2FXw9lG8Lwf7oNf23xxRojOqSjLbfmf%2F7nxKY9Vsdc8f4SJGKGsohiW1uRr70XHMSsCWXpz2NsbiSFwtySSG6150LjQPNy8vI8MJY55Utm%2FTAJZR2K%2FoLemD8WlPkqWDIxxv8m4YG9k0%3D Many things are unsigned or not hardened, which I guess is a question of enabling the appropriate things in the project? (Ignoring the syncthing binary itself since that build still points at 1.5.0.) |
I have created a PR to update to 1.6.1 but still the same problem. The build is located here: |
What is "the same problem" exactly? |
Syncthing itself is signed, hardened and notarized. However the other binaries in the package lack signing or hardening: notarization log for the 1.6.1-1 build |
Right, because it's not notarized, because see above. |
I think we are hitting two related issues:
|
Seems we already do deep codesign, but the hardened is not enabled for sparkle probably. No direct clue how to enable it.
|
Seems there are some problems with the dmg:
|
Apple has the error documented: https://developer.apple.com/library/archive/qa/qa1940/_index.html |
Seems the dmg app bundle is correct after some investigation. Only when copy it gets the quarantine attribute:
|
|
It works! |
@calmh I found a nice tool to check if an app is correct: |
Hi @calmh I have an issue with the new prerelease build from v1.4.2-1 git commit hash 3463cb3 located in TeamCity here.
Is there something wrong with the developer key?
The text was updated successfully, but these errors were encountered: