-
Notifications
You must be signed in to change notification settings - Fork 258
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
Issues Authenticating #295
Comments
Hello @raoulj! Can you try downloading version 2 from github releases since the cask is not updated yet(I wasn't the one to upload the cask and I am not sure on how to update it)? |
Ok! I just downloaded and I found that I had the same issue. Notably, however, the new download cached my attempt at login from my previous installation. I click the "Login to GitHub" button at the home screen and get immediately taken to the screen above. This is identical behavior to the cask installation. Would this shared datastore be the cause of the issue and getting me to some invalid state? |
Yes both versions use the same "storage" so it realises you already logged in in that window. Can you describe the steps when you first downloaded gitify and tried to login so I can reproduce the error? |
Sure thing.
|
Ok I think I'm getting closer. Once you are stuck on this screen can you open the devtools (of the github.com window) by press |
Ok I was able to reproduce it and fix it at #296. Will make a new release tomorrow as it is pretty late here. Will let you know once it's done. Thank you for reporting this issue! 👍 |
Awesome! Glad to help! |
Hello @raoulj! Version 2.0.1 is now out! Hope you can now login! |
Hello i downloaded 2.0.2 and i have a login issue :( |
@taylor325 I believe you are referring to this issue: #355 There are a couple of solutions in that thread. |
@JakeSidSmith Yes! Thank you! :) |
I make an account as direct when getting gitify via brew (
brew cask install gitify
). I get the following response:Everything seems approved but it is not letting me create an account?
The text was updated successfully, but these errors were encountered: