Skip to content
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

Can't login to Vortex #895

Closed
Raxdiam opened this issue Aug 25, 2018 · 3 comments
Closed

Can't login to Vortex #895

Raxdiam opened this issue Aug 25, 2018 · 3 comments

Comments

@Raxdiam
Copy link

Raxdiam commented Aug 25, 2018

Since update 0.16.0, I have been unable to login to Vortex.
Here is a recording of what happens: https://i.imgur.com/nbvboS0.mp4
Using the button in Vortex opens the default web browser, and asks me to authorize. After doing so, Vortex is brought to the front, but nothing changes.

Things I have tried:

  • Using different web browsers. This includes Chrome, Firefox, Edge, and Internet Explorer.
  • Uninstalling and re-installing Vortex.
  • Deleting other associated data (by default what is in AppData\Roaming\Vortex).

Log file: vortex.log
OS: Windows 10 Pro

@TanninOne
Copy link
Contributor

This is purely a display error. You are correctly logged in, Vortex just doesn't update its UI to reflect that. If you close Vortex after logging in and restart it you should be logged in ok.

The reason this is happening is that in 0.16.0 we had to switch one of the external libraries we were using because the old one has been abandoned in a buggy state but the replacement works differently in a subtle way.
This could trigger other similar errors where part of the UI remains "outdated" until you do something else that forces an update of that component.

@wieser1955
Copy link

Thanks for responding I had to reinstall to fix the problem but no big deal. thanks for the cool work your doing

TanninOne added a commit that referenced this issue Aug 27, 2018
@TanninOne
Copy link
Contributor

Turns out this wasn't at all what I thought it was. The "outdated UI" thing is a potential problem in 0.16 but not the cause of this error.
Actually it was just a line I had commented out for testing that somehow got committed. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants