"Install dependencies" button didn't show; thus weird behaviour

[dgxo]

After pressing the 'Login' button and giving access, I'm redirected to the local server where it says the following:

Error: Login request failed.
400, message="Bad status line 'HTTP/1.1 200 '", url=URL('https://apis.roblox.com/oauth/v1/token')

Tried with Firefox and Chrome (obviously won't make a difference since it's the backend).

When initially installing the plugin from Releases I was never prompted to install the required dependencies, so I encountered weird behaviour. See #issuecomment-2611404130.

[Nightriff]

Seems like the http client used in the plugin is unable to interpret the HTTP/1.1 200 as a valid status from the /oauth/v1/token Roblox API? I wonder if it has to do with that trailing space.

I'm unable to reproduce this, can you share which version of Blender you're running? And does this happen every time, occasionally, or just once?

[dgxo]

Every time I tried to login it failed and had the same result, or something with a very similar error which I don't remember.

Unfortunately now I am unable to reproduce this bug, but have instead encountered more weird behaviour
The response after completing the OAuth flow seems to depend on whether or not I select an account in the Accounts list on the OAuth page, and if so which account(s);

No account

Internal client error.
No creators were authorized during login

Group or my account + group

Internal client error.
'userFacingMessage'

Only my account

No response, web server appears offline

I only own one group, so maybe the behaviour is different with multiple groups???
I'm immensely confused on why any of this is happening, but here's my system info, with the username redacted for privacy reasons;
system-info.txt (MacOS w/ Blender 4.2.1 LTS, latest plugin version)
The exact same behaviour occurs with the latest Blender version, 4.3.2.

[dgxo]

Okay, just tried directly using the actual latest version directly from the repo instead of from releases, and it asked me to install the dependencies, which it didn't do when I first installed the plugin. It worked fine.
Not going to close this issue as it's still a bug that I was never prompted to install the dependencies.