You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2020. It is now read-only.
Had some weird issues just now, while testing the update to the login dialog:
when I logged in for the first time, there was an invalid connect.sid saved, and even after successfully logging in multiple times it didn't update the connect.sid - but it works now, just had to clear the textfield once. Still weird.
when you initiate a login while not connected to the internet, it throws an error but keeps loading indefinitely. It seems like you have to restart the application to try it again.
The text was updated successfully, but these errors were encountered:
I can't seem to reproduce the invalid connect.sid
I did some error catching and better logging for the internet issue; also it seemed like you weren't supposed to see the "login" button when there is no internet as there is a case for this button to show "No Internet"
You have to set an invalid connect.sid manually to the settings files and then open the application and try logging in, that's basically how it happened for me. Could also have been related to the outdated Gold check or smth.
Indeed, but if the login button is already there and I loose my connection I can still click it.
I'll pitch in here with some bug reporting, I had a prior version of the utils and I just reinstalled to the latest version pre-release.
I believe this is a 2FA issue, correct me if I'm wrong
When I started the app up it already had an sid (which it said was invalid). I tried using the login in feature with my details and I recieved an incorrect username/password.
I logged in online and used the sid following the prior method and the rest of the app seems to work fine.
The connect.sid issue being invalid sometimes happened to me in the past, this is not a 2FA issue, though 2FA of course doesn't work with the current login dialog (also now with APIv2 we know the endpoints for 2FA, that's something we could add).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
back-endStuff you can't see, but operates in the backgroundbugSomething isn't working
Had some weird issues just now, while testing the update to the login dialog:
The text was updated successfully, but these errors were encountered: