-
Notifications
You must be signed in to change notification settings - Fork 23
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
PSNAWPNotFound from a TrophyIterator on PS5 games #72
Comments
Note that I tested this on several PS5 and PS4 games, with similar results |
Can you try with the latest version of PSNAWP because it works for me. Also, assuming if you are looking up your own trophies you can use the client class from psnawp_api import PSNAWP
from psnawp_api.models.trophies import PlatformType
client = psn.me()
trophies = client.trophies("NPWR22810_00", PlatformType.PS5)
print(next(trophies)) This will save you some extra HTTP requests. |
I think I might know the issue. I switch platform type from string to Enum and passing in enum threw off the API wrapper. default case is for PS4 so which it is why it worked. but PS5 didn't |
I just tested it too, and indeed, getting rid of the string fixed it! |
Hello, I am currently trying to use PSNAWP 2.0.0 to retrieve my trophies from the last title I played.
Unfortunately, I am no able to get the trophies for PS5 titles. The TrophyIterator returned by the method User.trophies() greets me with an error 404 as soon as I try to iterate over it. This error could be raised in the case I have no trophy for this title, yet I have quite a few of those...
For PS4 games, I am able to iterate without any issue.
Here is a code sample to illustrate what I mean:
Here is the result when running the script:
As you can see, the TrophyIterator for the PS4 game return the first trophy of the list, but the PS5 TrophyIterator raises an error.
I have a hard time understanding why since I had no issue with the previous version of PSNAWP. I am trying to pin point what is happening, I will keep you updated if I find something!
The text was updated successfully, but these errors were encountered: