If a user has twitch client installed but is not authenticated into it then trying to connect twitch integration in Galaxy Client will spin indefinitely.
This is because of these lines:
It starts auth process and then immediately raises Invalid Credentials (which currently seems to have an issue in Galaxy Client).
I think it would be more intuitive to not cancel authentication right after starting it and possibly wait for it to finish (maybe watch the authentication window?).
Hey,
If a user has twitch client installed but is not authenticated into it then trying to connect twitch integration in Galaxy Client will spin indefinitely.
This is because of these lines:
It starts auth process and then immediately raises Invalid Credentials (which currently seems to have an issue in Galaxy Client).
I think it would be more intuitive to not cancel authentication right after starting it and possibly wait for it to finish (maybe watch the authentication window?).
Hope this helps.