Client unverifies itself and verification doesn't work #2111

Describe the bug

the client unverified itself while it was not even in use in the foreground, so half of the messages sent to me since i last opened it were not decryptable.

trying to verify it using another client simply didn't work, the popup for emoji verification never appeared on either client.

verification via recovery key seemed to succeed as you can see in this screenshot:

but if you exit and revisit this settings page, it shows as unverified again:

Reproduction

1. (somehow get the client to unverify itself)
2. click "Verify this device" or open the settings screen, then the "Devices" page
3. click "Verify Manually"
4. enter your accounts recovery key and attemt verification
5. exit and revisit the devices page or the account screen, the device has not been verified

Expected behavior

• the client shouldn't need to verify itself again for no reason
• verification should succeed and the device should stay verified

Platform and versions

Sable for Android Version 1.22.1 and 1.22.2.,
GrapheneOS (Android 17) on Google Pixel 8

Additional context

the following upstream cinny issue seems relevant:
cinnyapp/cinny#3067

before this happened, i logged into another account, didn't verify it, then switched back to the account i was using before. hours later, this happened. logging out of the second account didn't help.

i have not tried signing out and back in or reinstalling the application.