You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A friend was offline in TextSecure v2 until a few minutes ago. I had sent out two messages in the meantime: the first over push, the second over encrypted SMS.
The SMS was received by my friend, but got stuck in "Decrypting, please wait...", see bug #240. No Push message was shown as received.
After TextSecure restart, the SMS was decrypted. But the push message never showed up and seems to be lost. I'm wildly guessing that while SMS receive was stuck, the Push message was still stuck in processing queue (albeit being sent out first; but it was probably received later than the SMS), and after app restart it was just gone. The SMS was seemingly cached to be available and decryptable after app force close, but the GCM message wasn't.
The text was updated successfully, but these errors were encountered:
That is quite probable, yes. I don't know exactly, but my friend said they had just unlocked TextSecure again when the message was received, so TextSecure was probably closed due to the update when I sent out the messages.
A friend was offline in TextSecure v2 until a few minutes ago. I had sent out two messages in the meantime: the first over push, the second over encrypted SMS.
The SMS was received by my friend, but got stuck in "Decrypting, please wait...", see bug #240. No Push message was shown as received.
After TextSecure restart, the SMS was decrypted. But the push message never showed up and seems to be lost. I'm wildly guessing that while SMS receive was stuck, the Push message was still stuck in processing queue (albeit being sent out first; but it was probably received later than the SMS), and after app restart it was just gone. The SMS was seemingly cached to be available and decryptable after app force close, but the GCM message wasn't.
The text was updated successfully, but these errors were encountered: