-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unreliable data from API_GetUserRecentAchievements endpoint #2493
Comments
I have another report from another user with the same issue: |
@wescopeland Can I implement pagination on this API? I think this solve the problem. |
Sorry, I haven't investigated this issue and I'm not quite sure what the root cause of the problem is. Assuming I'm understanding the question correctly, I'm not sure why pagination might necessarily solve the issue if we're currently returning all the records. |
in the query has the limit of 500 |
Ah, I see. Thank you for that explanation. You're free to proceed fixing this. My requirements would be as follows:
|
Note: If the pagination parameters are not used, we'll need to preserve the exact response shape we currently have so we don't introduce a breaking change. |
I was going to ask about that, thanks for clarifying. |
Hello, one of my users pointed out that the Recent Achievements tab for them wasn't showing the most up to date data. I pulled his data from the API and it isn't showing anything past 6/7 even though he has earned cheevos since.
User: UltraGodAzgorath
Endpoint: API_GetUserRecentAchievements
Pics: 1st is RA.org progress page. 2nd is Postman API response
The text was updated successfully, but these errors were encountered: