Android failed update incompatible #543
Labels
No Label
android
arch
backlog
blocked-on-external
bug
bugbash
component/bindings
component/bine
component/connectivity
component/cwtch
component/tapir
component/ui
cwtch-1.14
cwtch-1.15
cwtch-beta-1.1
cwtch-beta-1.10
cwtch-beta-1.11
cwtch-beta-1.12
cwtch-beta-1.13
cwtch-beta-1.2
cwtch-beta-1.3
cwtch-beta-1.4
cwtch-beta-1.5
cwtch-beta-1.5.x
cwtch-beta-1.6
cwtch-beta-1.7
cwtch-beta-1.8
cwtch-beta-1.9
design
duplicate
enhancement
flutter
funding-needed
help wanted
hybrid-groups
in-nightly
in-progress
invalid
ios
linux
mac
need-replication-or-investigation
ops
packaging
post-stable
question
questionable
requires-more-effort-than-we-can-spare
rust
scheduled
stable-blocker
tails
testing-needed
tests
tor
waiting-on-fix-confirmation
waiting-on-new-flutter-feature
whonix
windows
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch-ui#543
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello! I installed your application directly from your website many months ago. The only way for me to update the application currently is to go to your website to download and install the new version manually.
Within the last month or so, aurora started picking up new versions but says there is a signature mismatch so it will not update it due to it being incompatible. The exact error is "INSTALL_FAILED_UPDATE_INCOMPATIBLE: "Existing package im.cwtch.flwtch signatures do not match newer version, ignoring!"..... Why is there a signature mismatch between the packages, the cutover should be seemless? Is there a plan to resolve this or am I going to need to uninstall and reinstall the app from the store to fix it? If I need to reinstall, please provide instructions on how to backup and restore the profile so I don't lose what I have. Thank you.
Android app incompatibleto Android failed update incompatibleHi! Thanks for the report, and sorry about the issue, you are correct that this should be seemless.
My first instinct is that the packages on Aurora have not been signed by us. We recently included fastlane metadata in our repo for packaging with fdroid but that work isn't yet complete.
To confirm: do you get the same error when attempting to install packages from our website?
Assuming the error is the same, and there is something wrong with our packaging process:
What version of Cwtch do you currently have installed (you get can this by going to
Settings -> About Cwtch
)?General Backup / Restore Information:
To back up / restore profiles, if you are on a more recent version of Cwtch you can use the Export Profile (https://docs.cwtch.im/docs/profiles/exporting-profile) / Import Profile feature (https://docs.cwtch.im/docs/profiles/importing-a-profile)
If your version of Cwtch does not have profile export or import (or if you are on a version of Android where it doesn't work (see: #512) the only way to export/import profile is to connect directly with
adb
and download the .cwtch file in the cwtch application folder (this folder contains all encrypted profiles) - you can then restore this folder when cwtch is update.Hey Sarah, thanks for the fast response! :) I have v1.8 installed. Aurora is trying to install v1.9. If it's available in the future through F-Droid, I'd rather add that repo instead so I look forward to that.
I do not get the error manually updated from your website, but since that is such a manual process I was hoping that I would not have a stale package in my update manager and continue to go through the manual update process.
Unfortunately when I go to export the profile through those instructions, the app force closes and the file exported has 0 bytes, empty.
Thanks for the update. Our goal is to definitely get Cwtch packaged properly for fdroid as soon as we can. (The tracking ticket is here: #141)
Sorry about that, we are hoping to have this bug fixed very soon.
Closing this in Favour of #141