Session closed by protocol error

Question

Session closed by protocol error

jajajack opened this issue 5 years ago · comments

jajajack commented 5 years ago

Bug Description

Steps to Reproduce (for bugs)

send a picture in a chat to a user
try to open that chat in threema web after that
error message comes up: Protocol error...
cuts connection from webinterface

Potential Solution

Delete the picture on your mobile app, then everything is working again.

Your Environment

Threema Web version: threema 2.2.1
Threema App version:
Browser name and version: safari 13.0.3
Computer operating system and version: MAC os Catalina 10.15.1
Smartphone operating system and version:

rugk · Answer 1 · Fri Nov 01 2019 02:25:03 GMT+0800 (China Standard Time)

You left an empty issue template, I guess there is really a little more information needed on why/how this happens…

jajajack · Answer 2 · Fri Nov 01 2019 02:26:20 GMT+0800 (China Standard Time)

sorry! new here....
fill it in right away :)

jajajack · Answer 3 · Fri Nov 01 2019 02:32:08 GMT+0800 (China Standard Time)

More clear now ? :)

Lenny · Answer 4 · Mon Nov 04 2019 17:36:03 GMT+0800 (China Standard Time)

Which app version are you using? Please, also fill in the information regarding the smartphone OS and version.

jajajack · Answer 5 · Tue Nov 05 2019 01:33:32 GMT+0800 (China Standard Time)

4.4.1 (2492)

…

Op 4 nov. 2019, om 10:36 heeft Lennart Grahl ***@***.*** ***@***.***>> het volgende geschreven: Which app version are you using? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#922?email_source=notifications&email_token=AGIQJBKNSIH6IT4SFABDANLQR7UIJA5CNFSM4JHPHITKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6U4PY#issuecomment-549277247>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGIQJBMQAZVTYP4EJL76HZ3QR7UIJANCNFSM4JHPHITA>.

Danilo Bargen · Answer 6 · Tue Nov 05 2019 19:52:31 GMT+0800 (China Standard Time)

We mainly had this issues with the app versions before 4.4.0. If you already used v4.4.1 when this problem occurred, then there must be a new bug.

In the iOS app, please navigate to “Threema > Settings > Advanced” and activate "Validation logging".

Then, once the problem occurred again:

In Threema Web, without reloading the page, click on "Troubleshooting" in the footer and send the logfile to the support (https://threema.id/*SUPPORT)
In the app, please navigate to "Threema > Settings > Advanced" and tap on "Share Log".

Please also let the support know at what time the problem occurred. This helps when diagnosing the issue.

I'll close this issue for now, but will re-open it in case the bug is in Threema Web and not in the app. Thanks for the report!