After recent twitch changes I decided to reinstall the github build from scratch because F-Droid release schedule is just too slow. Then, several days ago I found the application logged out after a day of inactivity or so and now I can't complete the login procedure:
the login screen appears as usual, but after entering name&pass and pin number the screen goes blank and displays
Error: -6 net::ERR_CONNECTION_REFUSED
in the upper part of the webview screen and "Having trouble logging in?" in the lower part.
After some digging in issues I've successfully applied the "change GQL redirect url to https://www.twitch.tv/passport-callback" solution from issues 271 and 277 so this issue can be safely closed.
I'm mainly creating it so others would have an easier time finding info and resolving similar issues on their own. :)
But I have to mention: it's a rather confusing process and those brief popup texts barely help with it. Fortunately, the url copied from the browser page (not from the address field!) was parsed successfully even with extra bits of text left so it's not that bad after all. :)
Also, apparently, reinstalling and clearing the application data does not reset the GQL redirect url field to the value proposed in those issues above, even with the newest version used.
After recent twitch changes I decided to reinstall the github build from scratch because F-Droid release schedule is just too slow. Then, several days ago I found the application logged out after a day of inactivity or so and now I can't complete the login procedure: the login screen appears as usual, but after entering name&pass and pin number the screen goes blank and displays
Error: -6 net::ERR_CONNECTION_REFUSED
in the upper part of the webview screen and "Having trouble logging in?" in the lower part. After some digging in issues I've successfully applied the "change GQL redirect url tohttps://www.twitch.tv/passport-callback
" solution from issues 271 and 277 so this issue can be safely closed. I'm mainly creating it so others would have an easier time finding info and resolving similar issues on their own. :) But I have to mention: it's a rather confusing process and those brief popup texts barely help with it. Fortunately, the url copied from the browser page (not from the address field!) was parsed successfully even with extra bits of text left so it's not that bad after all. :) Also, apparently, reinstalling and clearing the application data does not reset the GQL redirect url field to the value proposed in those issues above, even with the newest version used.