SMSsecure can't be updated with F-Droid #181

Closed
ciaby opened this Issue Feb 11, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@ciaby

ciaby commented Feb 11, 2016

Just flashed the latest image for the Nexus 5 (MMB29U.2016.02.07.14.31.34). If I try to update SMSsecure within F-Droid, it can't do it because it's signed by a different key. Obviously I can't uninstall it because it's in the base image :)

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Feb 11, 2016

Contributor

It's supposed to be that way. It's our own build rather than bundling a third party build as part of the OS. It's updated in the source tree and will be pushed out with the next build. I wanted to do a build already but I decided to wait until someone posts logs in #170 so I can roll that fix into the next build. It's starting to look like that's not going to happen so I'll just do the builds without it.

Contributor

thestinger commented Feb 11, 2016

It's supposed to be that way. It's our own build rather than bundling a third party build as part of the OS. It's updated in the source tree and will be pushed out with the next build. I wanted to do a build already but I decided to wait until someone posts logs in #170 so I can roll that fix into the next build. It's starting to look like that's not going to happen so I'll just do the builds without it.

@thestinger thestinger closed this Feb 11, 2016

@ciaby

This comment has been minimized.

Show comment Hide comment
@ciaby

ciaby Feb 11, 2016

I see, thanks for clarifying it :) Make sense actually, at least it's a trusted build.

ciaby commented Feb 11, 2016

I see, thanks for clarifying it :) Make sense actually, at least it's a trusted build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment