Skip to content
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

Wrong User Thin Trophy type returned from getUserTrophiesEarnedForTitle() #138

Open
TheYuriG opened this issue Mar 27, 2023 · 3 comments
Open

Comments

@TheYuriG
Copy link

TheYuriG commented Mar 27, 2023

Was wondering why i couldn't get the PS5 trophy progress from users and it was because the type specified was wrong. Below you can see what is actually returned with this method, instead of User Thin Trophy.

{
	"trophyId": 52,
	"trophyHidden": true,
	"earned": false,
	"progress": "416", // PS5 exclusive, on trophies that have tracking
	"progressRate": 89, // PS5 exclusive, on trophies that have tracking
	"progressedDateTime": "2023-01-23T09:04:57Z", // PS5 exclusive, on trophies that have tracking
	"trophyType": "gold",
	"trophyRare": 1,
	"trophyEarnedRate": "8.3"
}

This is for the game Forspoken: NPWR21656_00

I assume User Thin Trophy is just what gets returned from getTitleTrophies(), with the added earned and earnedDateTime, since I was never able to find any trophies that returned the properties trophyProgressTargetValue, trophyRewardImageUrl or trophyRewardName, but maybe I just didn't look on the right games.

Maybe this is Sony's PS5 exclusives only? Or are they only from getTitleTrophies() and unrelated to getUserTrophiesEarnedForTitle()?

If you are not in a hurry, you can assign me to do this PR since fixing this could be done basically at the same time I wrap up my pending PR.

@wescopeland
Copy link
Member

Hi @TheYuriG ,

I won't have a chance to take a look at this until later this week. If you'd like to take a stab you are more than welcome to. If not, I will try to investigate around Wednesday or Thursday.

@TheYuriG
Copy link
Author

Access Denied

Seems like you are doing something wrong with the authentication endpoint, which is unrelated to this issue.

Maybe go though the documentation again and make sure you are following the steps correctly and open a separate issue if that still doesn't. I've logged in just fine yesterday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@wescopeland @TheYuriG and others