-
Notifications
You must be signed in to change notification settings - Fork 50
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
Every start of desktop app I need to log in again #227
Comments
такая же проблема |
Same problem. I can use SchildiChat on Android and Linux, but i can't use it on Windows. |
Same problem. |
Duplicate of #170 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possibly related with #170
Whenever I open the app, it will show me "Connection to the server was lost" message (might not be literally, app is in my local language, this is translated back).
This happens consistently since I started using Schildi on windows. This does not happen on android version.
To make it work, I need to log out and log back in, do the setup with android (scanning qr) and wait for keys to sync.
After re-logging as long as I don't quit the app the connection stays up indefinitely (max tried 3 months, my system is fairly high uptime - therefore it doesn't look like exactly #170 but still might be related)
What's more, in that disconnected state, Im unable to enter settings -> about.
While in that state, in console it looks like it's calling the server without token and getting 401's, but actually it sends authorization header, but it's clearly wrong:
authorization: Bearer [object Object]
I looked deeper and it seems that when
authedRequest()
is called, it usesthis.opts.accessToken
for header.This has actually value that looks like AES encrypted or something similar, it's object with
ciphertext
,iv
andmac
fields.That's all I know.
Other context:
Version: SchildiChat: 1.11.30-sc.2 Olm version: 3.2.12
OS: Windows 10 (2021; 10.0.19044.3803)
This does not happen on Element (which I have side by side for different matrix server).
The text was updated successfully, but these errors were encountered: