Join GitHub today
OMEMO after Phone restore: no messages sent / received / shown on a 2nd device #2227
Steps to reproduce
SOLUTION: To solve this issue, I reset the OMEMO crypto keys on both devices.
My guess is that the AXOTL ratchet got out of sync due to the restore and thus the receiving device could not decrypt the message.
PS: I did not try to reproduce this issue OR gathered logcat before resolving this issue by resetting the OMEMO keys.
@mimi89999 do i also have to disanble accounts when back using using nandroid (from recovery in offline state)?
btw.: would it be possible to detect access of bsckup software and disable accounts when detected
I just reproduced this bug but I don't really know how. It was not restoring a backup but something between recreating keys, enabling/disabling presence on one side.
There was no real error message but this is the logpart that was printed when the client received a message but was not displayed:
and this is the part from the phone sending the message:
I had the same problem (and logcat output) after restoring a Titanium backup. :-|
Here is my relevant part of logcat:
referenced this issue
Oct 24, 2017
Reproducing this is quite easy (as I sadly discovered):
So the idea to recover would be to have an option to end the OMEMO session and start a new one, only for this specific conversation without having to scrap all keys for all contacts.