-
-
Notifications
You must be signed in to change notification settings - Fork 170
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
Amazon Prime Gaming in game content claims fail #208
Comments
The new sub pages create errors like
|
Yeah it looks for a button called "Claim now" - however the button is just called "Claim" now and thus it fails. |
The button was renamed to "Claim" instead of "Claim now" this causes / fixes vogler#208
[AggregateError: All promises were rejected] {
]
] same :C |
The button was renamed to "Claim" instead of "Claim now" this causes / fixes vogler#208
I'm seeing the same issue after updating to latest code. I confirmed prime-gaming.js has the two changes listed in the PR, but the bot still sits on the pre-claim page. Edit: When the bot reaches this page, it freezes If you manually click "Claim" the bot continues. Otherwise it will time out and move on without claiming the item. Edit edit: I describe this as "pre claim" because it is also the interface used when multiple claims are available for the same game. This isnt the page where the actual claiming happen, it is simply a list (sometimes of 1) of current offers for the game. Edit edit edit: Also, as @Mrgaton mentioned, there is yet another button labelled as |
Hmm even with the newest image it still looks for
Could it be that a new one was never published? |
OK I think I found the issues: The latest image is only published under This works much better and it recognizes when I don't have an account linked: However eventually it still fails on a couple of titles with one of two errors: This is because our friends at Amazon sometimes use a button and sometimes use an anchor link in the HTML: So I guess we need to make the script versatile enough to check for either a button or a link with the given text - or instead look for the css class |
On latest of the Printed output:
Logs:
|
Probably due to #229. However, the code looks like it should publish free-games-claimer/.github/workflows/docker.yml Lines 32 to 36 in 9f97805
Don't use |
Why not |
Further addition: |
OK I tested it again and now it should work with #274 . I changed the selector to account for both types of buttons and in case there are more than one account link buttons, it will take the first one. |
Can check/merge after lunch. |
Yeah I guess that could also work |
Use `.tw-button` css class over `button` html element selector
Working well, small issue I'm noticing is that after the claim this timeout can linger instead of detecting the successful claim:
|
@sealldeveloper I ignore the timeout now. However, it would be better to add a case for this. For which item does this happen and what is there instead of a code or account linking? |
@vogler This has happened with:
The result is it properly being claimed but the output is just the error from timeout then it moves to the next one after waiting the timeout. I've also noticed with EA accounts (even when properly linked) will display to 'link the account' again, resulting in never claiming the EA rewards. |
It appears that the in game content claims have all started using the "multi week" claims, where you need to click not only into the games page, but also "claim" on the specific reward you want in order to actually reach the claiming page. If you watch the bot work, you'll see what I mean because it stalls for a long while waiting for the content it expects.
The text was updated successfully, but these errors were encountered: