If keyless Console sign-in isn't available, login now warns and falls back to API key.
What's wrong with this entry?
If keyless Console sign-in is not available where you are, login now warns and continues down the API-key path rather than erroring out. The waiting and error screens show the reason inline.
- Triggered by the shape of the server's error response, not by any local flag.
- The message ends with ", so this sign-in will create an API key."
Keyless Console sign-in unavailable here, continuing with the API-key sign-in:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth