Unencrypted messages stuck saying "Decrypting, please wait"

[shenki]

Observed by myself and another user on a Nexus 5 and Nexus 4, both running Android 4.4.2 (stock) and TextSecure 2.0.1. When receiving plaintext SMS from non-TextSecure users the message gets stuck in the inbox say "Decrypting, please wait".

Closing TextSecure and re-starting results in successful display of the message. Both users are not using a passphrase.

The symptoms are the same as #240, so this may be the same bug.

[ChristophWurst]

I experienced the same issue one my Nexus 4 (Android 4.4.2 stock).

For me it seems to only occur when receiving googles 2-step verifcation codes where sender is shown as "Unknown"

I could see the message after a forced stop and restart of TextSecure.

[crackercho]

I am experiencing exactly the same bug as @shenki. Android 4.4.2 (stock) on Nexus 4, TextSecure 2.0.2 (I received the update about an hour ago). No passphrase on TextSecure. When TextSecure is not running and when I receive an SMS and I click on the notification, TextSecure opens the conversation and the message reads "Decrypting, please wait" in italic. After closing the app and relaunching it I can read it just fine.

[moxie0]

@shenki are you also configured with no passphrase in TextSecure?

[crackercho]

@moxie0 Shenki said in his report that "Both users are not using a passphrase" so yes. Also, I'd like to add to my report that the same text "Decrypting, please wait" appears as the notification text before launching TextSecure.

[shenki]

@moxie0 correct, no passphrase

[Krozar]

Just adding myself and my wife to this list. Both running the latest AOKP nighly (2/25/14) on the Galaxy Nexus (Toro), with no passphrase. This happens when receiving SMS messages from non TextSecure users. I had not yet found a way to resolve the issue, other than to wait it out (anywhere from a couple minutes to several hours), but I'll try some of the suggestions mentioned above next time I encounter the issue. BTW, we both installed the app for the first time a week ago,v2.0.3.

[moxie0]

This should be fixed in 2.0.4