RiotGames
[BUG] account-v1/GET_getActiveRegion fails with 500 on some newly created accounts (e.g. NA1 `WHITEWOLFF#270`)
https://github.com/MingweiSamuel/Riven/issues/96
Bug Description
A few accounts cause getActiveRegion to return 500 errors. Getting summoner returns 404. Seems they may be a new kind of account (but I haven't been paying attention to what Riot is up to)
Examples, NA1/AMERICAS:
{"gameName":"WHITEWOLFF","tagLine":"270"}
{"gameName":"INTIK","tagLine":"270"}
From @NotMiaow:
this one is my cofounder, he created his accounts to test Oauth2
For these accounts, account-v1/GET_getActiveRegion returns a 500 server error for both "lol" and "tft"
Getting summoner_v4/get_by_puuid returns 404.
Expected Result
account-v1/GET_getActiveRegion should return 404 or a different user-facing error code, instead of having an internal error. summoner_v4/get_by_puuid returning 404 is fine though that is a new behavior-- previously all valid PUUIDs I came across had a valid summoner.
Actual Result
account-v1/GET_getActiveRegion 500 internal server errors
Developer Impact
Unusual edge cases that develoeprs need to handle.
Indication of a bug lurking within Rito code.
- Frequency: Every API call for affected accounts
- Severity: Can be handled by developers
Player Impact
Indirect
