LibreSignal update signature conflict?

asked 2017-09-06 11:53:39 +0200

496 ●15 ●24 ●29

updated 2017-09-06 12:28:35 +0200

I've installed LibreSignal on my JollaC, I've been able to add support for extra devices (like a Chromium browser on a desktop Linux) and encrypted communications seem to work as expected. However, when updating LibreSignal (and a new version seems to come up on a fairly regular basis) there is an application signature conflict, and to update you need to uninstall and reinstall LibreSignal. This means you also need to re-register your phone number and your extra devices.

Am I doing something wrong, does this application signature conflict happen to anyone else?

Comments

Afaik, LibreSignal was abandoned in 2016 (see https://github.com/LibreSignal/LibreSignal/blob/master/README.md ) and is no longer updated. You may want to look for another messenger.

From where did you install it?

ghling ( 2017-09-06 13:06:37 +0200 )edit

I am referring to the sofware available at the Jolla store as "LibreSignal Jolla Edition", which (if I've understood correctly) actually should end up installing software compatible with the current SIgnal.

ExTechOp ( 2017-09-07 10:10:21 +0200 )edit

answered 2017-09-06 14:10:24 +0200

leszek
10282 ●101 ●145 ●150

updated 2017-09-06 14:13:22 +0200

If you mean the LibreSignal Jolla Edition. It requires registering when installing an update. This is a change Signal does. If you update it will then keep you updated with Signal instead of LibreSignal. LibreSignal is abandoned and the Jolla Edition only allows you to chat and switch to official Signal APKs if you need updates.

edit flag offensive delete publish link

Comments

Hi leszek, I realize you're the author of this software. What happens to me is that I installed your software from the Jolla store labeled as "LibreSIgnal Jolla Edition". I then get suggested to update it, and when I try updating it I get told "Signal: App not installed. An existing package by the same name with a conflicting signature is already installed." At that point my only choice would be to uninstall it to get around the signature problem, and then I'd be pretty well back where I started. Suggestions?

ExTechOp ( 2017-09-07 10:17:49 +0200 )edit

Nothing I can really do from my end. They did this change on purpose it was working fine before. What you could try to do it saving the settings manually by trying to find where they are saved and then uninstall the LibreSignal and install Signal after that restoring the settings.

Though this is untested. Best would be to just stick to the version you have and ignore the upgrade message.

leszek ( 2017-09-07 10:53:23 +0200 )edit

There is a Import/Export option in Signal. Click the 3 dots on the upper upper right. Backup the way you want it. Uninstall LibreSignal and get the 'official' apk e.g with yalp app from f-droid. You may have to register again and import your backed up messages after that.

They have implemented running signal without google services some time ago as 'fallback' option so imho there is no reason to use leszeks' version atm. correct me if i am wrong

daywalker ( 2017-09-07 11:44:00 +0200 )edit

I actually ended up manually uninstalling LibreSignal and going for the apk installation from https://signal.org/android/apk/ which seems to work just fine. Would it make sense to remove the old LibreSignal package or just make it a direct installer for the apk?

ExTechOp ( 2017-09-07 12:04:11 +0200 )edit

The old package is still working and has no security issues. So it can be used. You are not allowed to share the official Signal APK or download it any other than the official way.

leszek ( 2017-09-07 12:05:52 +0200 )edit

LibreSignal update signature conflict?

Comments

1 Answer

Comments

Question tools

Stats

Related questions

LibreSignal update signature conflict?

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions