-
Notifications
You must be signed in to change notification settings - Fork 25
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 broken #225
Comments
There was a new version released a few days ago. v1.3.6. Did this version not fix login for you? |
I'm on 1.3.6 and it sadly is still taking me back to the login page after selecting my user. :( |
Version 1.3.6 did not fix the issue for me at all. Version 1.3.5 was working fine for me last I checked, but that was 2 weeks ago so I can't be certain when. |
I can confirm that the latest version (1.3.6) and before are not working. There's a button to enter the iksm_session manually I know, but it's really hard to explain to someone else who doesn't really know about scripts or lacking of PC knowledge. Could you make it easier to get the session automatically or with an easy step by step on UI? The squid-track with modern UI should be the best one for the most of players who don't use the terminal. Maybe you can see the windows version of splatnet2statink which I tried and the steps kinda easy without proxy or something else. |
Just a guess, but app version probably needs to be bumped as well (to update user agent header) because that's what I did on my own implementation when I request the hash from elifessler. I haven't run squid tracks on my machine currently so I'm not sure if that will fix it. |
Actually, yes. The root cause is that the v1.3.6 release uses the old userAgentVersion, which didn't bump into 1.11.0. You can easily fix it via @mathewthe2 Could you rebuild the installers for the others? Just can't figure out how to build it yet... |
login has been broken for about a week now and it just keeps looping from the squidtracks login page to the nintendo login page and back. is there any way we can get this fixed?
The text was updated successfully, but these errors were encountered: