Open kolAflash opened 7 years ago
Threema ID is working again in the demo after using the Android Threema app to restore the ID from the threema.id
file and receiving the offline-messages from the server.
So it looks like demo can't receive the waiting offline-messages and that - in some way - blocks the demo from receiving further messages.
I can confirm this -- sort of (on testing code, 2 days ago)
sometimes (rarely!) when starting the demo and there are more (4 for example) offline-messages waiting, there is no receivedMessage-"event" (no new entry in the channel). You can not send and there are no new receivedMessages anymore.
When hard restarting the demo several times, you suddenly get one receivedMessage, which is the latest you sent to the demo. The other (first 3 for example) messages seem to be lost. (On your mobilephone they don't have viewed-state, but the latest does).
I think this issue is the reason for what kolAflash describes here. Issue #16 on o3ma/o3: you have to receive before you can send
Demo is working fine. Started demo program on my Linux notebook, send two messages from the Android Threema app on my smartphone and receiving answers from the bot.
Closing and starting the demo again also worked fine and it continues to answer messages from my smartphone.
But then I send one message from my smartphone while the demo wasn't running on my computer. An "offline message"! After that, the demo did not receive or answer any more messages.
The demo also stopped answering to non-offline-messages.
Only fix/workaround was to delete the file
threema.id
on my computer and let it generate a new Threema ID.