-
Notifications
You must be signed in to change notification settings - Fork 4
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
Login failed. Check your login credentials. #25
Comments
Note: not a Rogers login. |
Log file: http://xbmclogs.com/pjxpqoegf |
Checked the settings.xml and the username is set to [email protected] and the password is correctly set too. |
Can you install this version: Then attempt to login. After it fails check you kodi userdata/addon_data/plugin.video.nhl-... for the cookies.lwp file and post it's contents here. |
Sorry, it's on a Fire TV, so no copy/paste option for that file. I did manage a photo though: |
Ok, I think i see what might be the issue. I've updated that zip file. You can install again and post your results here. |
Downloaded zip. |
Ok, try this version please: |
This works. Logged in. Can play recent games. No live games on at the moment to test, but assume all is OK. Thank you for the fast response! |
Good deal, I pulled the changes to the master as well. |
still not working for me. any advice? |
Neither here. However I only used the normal username (not the email).. but I guess I tried both multiple times. |
I get check your credentials, Sony tv,rogers login. Please help. |
Using Kodi on a Fire TV.
Entered email: [email protected]
Entered my password
I receive the error "Login failed. Check your login credentials."
I have tested those credentials on the gamecenter login page:
They are 100% correct. I have re-entered them multiple times to check.
I think maybe around here:
https://github.com/dannyellis/plugin.video.nhl-gamecenter/blob/9c5210d39fc866bec27432eeb12671ad51af8d5e/resources/lib/userinterface.py#L64
But not a python dev, so just a guess.
Using latest master, commit d945383.
The text was updated successfully, but these errors were encountered: