-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Auto update on macOS #1315
Comments
Is debug logging enabled? |
Yep, this is what I see in my logs:
|
I cannot yet check code, but you can try to: logger.warn = logger.info |
That seems to have fixed it. I still have some error because the app is not correctly signed, but I'll look into it as soon as I can |
I get a warning about the application not being signed (and it's not yet), then the new version on s3 is detected as an available update, but the download does not start or it gets stuck. Here are the logs:
|
For Mac autoupdate app is required to be signed |
@develar is the signature mandatory even for testing purposes ? |
Always required. You can use free |
👍 ok I tried a dummy Mac Developer certificate and it worked! Now I've got to generate a good one. I do not use Xcode, but maybe there is a way to get one without it. Thanks again |
Move to close? |
This is not related to this issue (sorry). @dventurino where do you get the free/dummy mac dev certificate? |
This issue is not closed because |
@ccnokes I had a mac development certificate generated on machine (with Xcode) at work. It's good enough for development purpouse, but not for production. |
@dventurino Where in Xcode do you create this? I'd created my own in osx keychain before but not sure where to get a free "mac development" one from within Xcode? |
@alexcroox |
@dventurino thanks, and I assume if I'm exporting this I can share with other team mates who can use it to sign new releases from their own machines with it? (it's an internal tool so a development cert is fine for auto updates) |
Yes, I use Keychain Access to export the credential and key as a .p12 to be imported on another mac via Keychain Access. |
@alexcroox yep! As @bill-pixvana said, you just have to share with them the .p12 file. |
TypeError — Obsolete since electron-updater 2.0.0 (will be released today). |
Similarly to issue #1310 , I'm setting up the auto-update feature on macOS as well. The publishing process is ok, but I've got an error during the update process:
This is the code looking for any updates:
The text was updated successfully, but these errors were encountered: