-
Notifications
You must be signed in to change notification settings - Fork 107
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
Signaling: Subsequent responder handshakes trigger a protocol error #799
Comments
Some more information: Today, I tried to reconnect (using web-beta.threema.ch) and the 12 % issue occurred again (also see #792 (comment)). However, after about 3 minutes, the 12 % disappeared and the display above appeared (with the disabled password input). When I look into the logs, the app definitely got the push notification. Here detailed logs. At 13:43:25 I clicked "Verbindung aufbauen" on web-beta.threema.ch: Logs from web-beta.threema.ch
message_log.txt
What's perhaps also interesting: In the Android app, it says the Threema Web session was recently used at 13:45: |
This is a bug in the SaltyRTC Client JS lib: saltyrtc/saltyrtc-client-js#114 @dbrgn please take a look at the second comment. It looks to me as if the app establishes multiple SaltyRTC connections (which it should not do, at least not for the same session) but dispatches to a single, central state (which I guess is a secondary issue). |
Should have been resolved by 014a05a |
Using Threema Web's beta, I encountered the following problem today:
After the reconnection did not work, Threema Web showed this screen (note that the password is still kind of displayed but I cannot edit it, the input field is disabled).
Full logs
Your Environment
The text was updated successfully, but these errors were encountered: