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

[Bug] Crash when updating Signal #659

Open
h-2 opened this issue Sep 10, 2024 · 5 comments
Open

[Bug] Crash when updating Signal #659

h-2 opened this issue Sep 10, 2024 · 5 comments

Comments

@h-2
Copy link

h-2 commented Sep 10, 2024

Describe the bug

Calyx Repo just updated Signal (finally!).
But now NeoStore crashes when trying to download it. This is really annoying, because the current signal version will become unusable in a week.

To Reproduce
Steps to reproduce the behavior:

  1. Activate the Calyx Testing Repo
  2. Find Signal
  3. Press install
  4. App crashes during download even if it is kept in foreground

Expected behavior

Shouldn't crash.

Screenshots

Relevant information:

  • Device: Pixel 6
  • Android Version: 14
  • ROM: GrapheneOS
  • App's Version: 1.0.5
  • Disabled battery optimization for Neo Store? Yes
  • What is your selected installer? Default
@h-2
Copy link
Author

h-2 commented Sep 10, 2024

If I select the System-Downloader in the options, it doesnt crash while downloading, but then it fails to verify the signature afterwards.

@machiav3lli
Copy link
Member

I face neither issues. If the signature fail it could be that you've Signal from another source. Try if disabling signature verification in settings/updates help, if not then you surely have Signal from another source.

That said, if you'd like Signal with timely updates uninstall yours (don't forget to backup) and install Signal-FOSS from TwinHelix's repo.

@h-2
Copy link
Author

h-2 commented Sep 10, 2024

If the signature fail it could be that you've Signal from another source.

No, I have from Calxy source.

Calyx is aware of the issue, it happens because Signal has rotated their Signing key: https://community.signalusers.org/t/beta-feedback-for-the-upcoming-android-7-10-release/61489/60

This caused problems in the FDroid repo software resulting in a delay of the Signal builds. Those are now fixed and the official F-Droid clients should be able to handle the change. But I was told that they wouldn't be surprised if other clients had problems updating this particular package.

@h-2
Copy link
Author

h-2 commented Sep 10, 2024

I can confirm that F-Droid basic client is able to successfully upgrade the Signal App from the same Repo that NeoStore failed with.

@machiav3lli
Copy link
Member

Try if disabling signature verification in settings/updates help, if not then you surely have Signal from another source.

I would've been interested in this point, but it seems you didn't check this (too late, I guess). That said, I'll see what needs to be implemented to support signature rotation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants