Encounter "Unfortunately, Silence has stopped." when initiating secure session
Created by: yankee14
Bug description
I reported #543 (closed) a few weeks ago, and today I noticed that an unstable build was available which included the fix for #543 (closed). I installed unstable, opened a conversation with someone for whom a secure session was already initiated from before I updated, and who did not upgrade to unstable along with me--that is to say, I did not go through any of my conversations before upgrading and end currently running encrypted sessions, and, none of my other contacts using Silence upgraded to unstable with me.
I sent several messages to this contact, and I cannot remember whether the lock icon at the top was closed or open. When this contact replied to me, the chat (understandably) displayed an error message for each of their replies, something like, "Contact is replying to an already-encrypted session." I take that to mean that their phone still thinks I have some old key which I (understandably) lost when upgrading.
After I saw this error message, I noticed the lock icon at the top was an open shackle. I tapped it to initiate a secure session, and this is where the app crashes. It crashes every time I initiate a secure session.
The link to the debug log below was after I made it crash in exactly this way three or four times, and before I tried any of my own troubleshooting.
Tried some troubleshooting
Unable to talk to this contact at all because of the crashing, I opened F-Droid and tried reverting back to the previous version, 0.15.2. F-Droid said something like "app cannot be installed for unknown reason." So, I completely removed Silence altogether, and tried installing 0.15.2 again. It succeeded, but all settings were reset to default and all my conversations were lost--importing did not work.
I started a new conversation with the contact and tapped the lock icon. It did not crash, but I did not receive any message back from their phone completing the key exchange. I have a feeling their phone is prompting them about a new fingerprint or something...
I'd also like to point out that a different contact got a new phone recently, installed Silence, and the app will not even start. It apparently just crashes with the same error message in the title, "Unfortunately, Silence has stopped." I cannot produce a debug log of it. EDIT: See #557 (closed)
How to reproduce
- Open a conversation in Silence (maybe after updating versions, maybe not).
- Initiate a secure session with that person (maybe their Silence thinks a session is already in progress, maybe not).
- Observe a crash
Actual result: Silence crashes, "Unfortunately, Silence has stopped." Expected result: A secure session should be started without crashing,
Device info
Device : lge LG-LS980 (cm_ls980) Android : 5.1.1 OS Host : cyanogenmod App : Silence 0.16.0-unstable
Link to debug log
EDIT: I got the contact to end the secure session with me, upgrade their Silence to 0.16.0-unstable while I had 0.16.0 installed already. The moment they initiated the session, my Silence crashed and will not start at all. To get it to start I have to uninstall and reinstall Silence. For now, we will both just run unstable without an encrypted session. Incidentally, #543 (closed) persists in 0.16.0, seems fixed in 0.15.4.