Bug #2920
After upgrade to 13.1.2, no messages displayed in chat window
| Status: | Closed | Start date: | 01/28/2014 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | 02/28/2014 | |
| Assignee: | n8fr8 | % Done: | 0% | |
| Category: | - | |||
| Target version: | v14 - Armadillo's Agram | |||
| Component: |
Description
1. Messages I send are sent (the other person receives them) but they never appear in my chat window.
2. Messages they send me never appear in the chat window. They do appear in the Notification area, but of course each new message overwrites the old one.
3. So, the chat area stays completely blank.
This is on Replicant (Android) v4.0, with OTR on, in an encrypted conversation.
I am using the version of the app from your f-droid repository.
Related issues
History
#1 Updated by johns almost 4 years ago
Sorry, forgot to mention that it's on a Nexus S.
#2 Updated by b33rg1t almost 4 years ago
I can confirm this. It is a critical bug, as this makes the whole Application useless. And even worse, because people would write you and the messages would not be readable.
Anyway, when installing the application from Google Play it works. Please package well for F-Droid. I think one of the worst things of an Android phone is to be forced to use Google's sources.
#3 Updated by dominik almost 4 years ago
+1 from me. Chat window is empty.
#4 Updated by dominik almost 4 years ago
No security pin is needed to open chatsecure (after it was sent to background). Notification says: You received an unreadable encrypted message. This is possibly related.
#5 Updated by dominik almost 4 years ago
^^^
Android 4.2.2 cyanogenmod 10.1
#6 Updated by n8fr8 almost 4 years ago
- Due date set to 02/28/2014
- Status changed from New to In Progress
- Assignee set to n8fr8
- Priority changed from Normal to Urgent
- Target version set to v14 - Armadillo's Agram
I have been working on this, but just updating the ticket now to show it. Thanks for your feedback and patience.
#7 Updated by n8fr8 almost 4 years ago
FYI, the problem is fixed if you wipe the data and start fresh, or uninstall/re-install. HOWEVER, we do hope to fix it properly with a db upgrade in the next update.
#8 Updated by n8fr8 over 3 years ago
- Status changed from In Progress to Resolved
#9 Updated by n8fr8 over 2 years ago
- Status changed from Resolved to Closed