Skip to content
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

App update failed Something went wrong while updating the app. InvalidSignature error while trying to update from 0.14.8 to 0.14.10 #7570

Open
darkred opened this issue Mar 10, 2025 · 2 comments
Labels
bug Something isn't working 🎉reproduced🎉 The issue could be reproduced by following the instructions

Comments

@darkred
Copy link

darkred commented Mar 10, 2025

Version

0.14.8

Operating System

Windows

Distribution Method

(from the main screen of the app, via the "Update to 0.14.10" button)

Describe the issue

I have GitButler 0.14.8 installed on Windows 11. I opened it today and I got the "New version available. Update to 0.14.10" prompt. Clicking the "Update to 0.14.10" button unfortunately results in the following error message to the bottom right of the window:

App update failed
Something went wrong while updating the app.

You can download the latest release from our downloads page.

InvalidSignature

Image

How to reproduce (Optional)

  1. Launch GitButler 0.14.8. See the "New version available. Update to 0.14.10"
  2. Click the "Update to 0.14.10" button.
  3. You'll get the "InvalidSignature" error mentioned above.

The above occurs consistently.

Expected behavior (Optional)

The update should complete successfully.

@darkred darkred added the bug Something isn't working label Mar 10, 2025
@darkred
Copy link
Author

darkred commented Mar 10, 2025

I also downloaded the x64 binary (GitButler_0.14.10_x64_en-US.msi) and its digital signature is ok.

Image

@Byron Byron added the 🎉reproduced🎉 The issue could be reproduced by following the instructions label Mar 11, 2025
@Byron
Copy link
Collaborator

Byron commented Mar 11, 2025

Thanks a lot for reporting, and for going the extra mile to check if the signature is broken for the downloadable release as well.
I could easily reproduce the issue on a Windows VM.

As the package for the auto-updater is a separate artefact, it's very possible for it to have its own issues.

CC @ndom91 and @krlvi as the ones who know how to tame Windows code signing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working 🎉reproduced🎉 The issue could be reproduced by following the instructions
Projects
None yet
Development

No branches or pull requests

2 participants