Problem Description
I receive invalid/unencrypted data occasionally. I have example of data received and when it happened at the bottom of this issue.
Expected Result
To always receive the same data for the same user when I use the same API token
Actual Result
From time to time, I happen to get unencrypted data. Example at bottom of issue.
Developer Impact
In my case, it doesn't seem to break anything yet, it simply just causes a bit of a mess in my database.
Frequency: When its bad, it happens every other day, but generally once or twice a month. When it happens, it happens for a short period for all my requests to obtain user information as far as I can tell.
Severity: When it happens, I register invalid duplicates of all active users, which causes a mess in my database.
Cost: In my case, pennies and a headache
Efficiency: For a short while I make a bunch of API calls for invalid users. I of course register the response from your servers, and hold off on those failed requests, but I would estimate I make 5-10% more requests, which all result in errors. If I didn't hold off on requests for users that recently failed, the amount of requests would have doubled.
User impact: Users won't notice this, unless the extra requests causes my API token limit to get used up.
Region: I've experienced it for EUW and NA1 users. I don't think I have active users on other regions currently.
I cannot reproduce the error, it is periodical and seems to be without a pattern
Example
I picked out one user for this example. I dont know if the data is sensitive or not, so I will not use the exact data i received, simply show the format with bogus data.
Account ID: I would receive a seemingly random 9-digit number, for example 227583624
Summoner ID: I received a seemingly random 8-digit number, for example 63846739
PUUID: I received a UUIDv4 for this, for example 0a951dbd-fbb5-4384-a317-6da19b33d214
Date it happened: Around 06:17AM, 12th June 2024 GMT+2. This is the timestamp of when I received my error. I would assume my program obtained the wrong information maximum 5 minutes before this, but probably only 30-60 seconds before.
It happened again, this time for an EUW user. It happened around 9:01PM, 13th June 2024 GMT+2. The Account ID was only 8-digits this time, I assume it's because the account is newer.
Bug Description
Occassionally I will receive what seems to be unencrypted user-data (account id, summoner id and puuid). It happens when I look up user information on https://developer.riotgames.com/apis#account-v1/GET_getByRiotId with gameName and tagLine and use the obtained PUUID to get League of Legends account information from https://developer.riotgames.com/apis#summoner-v4/GET_getByPUUID
Problem Description
I receive invalid/unencrypted data occasionally. I have example of data received and when it happened at the bottom of this issue.
Expected Result
To always receive the same data for the same user when I use the same API token
Actual Result
From time to time, I happen to get unencrypted data. Example at bottom of issue.
Developer Impact
In my case, it doesn't seem to break anything yet, it simply just causes a bit of a mess in my database.
Frequency: When its bad, it happens every other day, but generally once or twice a month. When it happens, it happens for a short period for all my requests to obtain user information as far as I can tell.
Severity: When it happens, I register invalid duplicates of all active users, which causes a mess in my database.
Cost: In my case, pennies and a headache
Efficiency: For a short while I make a bunch of API calls for invalid users. I of course register the response from your servers, and hold off on those failed requests, but I would estimate I make 5-10% more requests, which all result in errors. If I didn't hold off on requests for users that recently failed, the amount of requests would have doubled.
User impact: Users won't notice this, unless the extra requests causes my API token limit to get used up.
Region: I've experienced it for EUW and NA1 users. I don't think I have active users on other regions currently.
I cannot reproduce the error, it is periodical and seems to be without a pattern
Example I picked out one user for this example. I dont know if the data is sensitive or not, so I will not use the exact data i received, simply show the format with bogus data.
227583624
63846739
0a951dbd-fbb5-4384-a317-6da19b33d214