-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demo stops working after offline message #7
Comments
Threema ID is working again in the demo after using the Android Threema app to restore the ID from the 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). 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. |
I think this issue is the reason for what kolAflash describes here. |
Also solved send-receive problem on startup. See: o3ma#7
sendMsgChan) and fixed o3ma#7 by putting sendTestMsg into a separate thread.
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.The text was updated successfully, but these errors were encountered: