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

Still unable to claim games with latest build #16

Open
chaoscreater opened this issue May 26, 2021 · 6 comments
Open

Still unable to claim games with latest build #16

chaoscreater opened this issue May 26, 2021 · 6 comments

Comments

@chaoscreater
Copy link

I've deleted my Heroku project and Github fork and set it up from scratch.

I'm still getting the same issue.

I'm not using any cookies this time.

image

2021-05-22T05:28:02.750969+00:00 app[web.1]:         at TLSSocket.SMTPConnection._onSocketData (/usr/app/node_modules/nodemailer/lib/smtp-connection/index.js:189:44)

2021-05-22T05:28:02.750969+00:00 app[web.1]:         at TLSSocket.emit (events.js:314:20)

2021-05-22T05:28:02.750969+00:00 app[web.1]:         at addChunk (_stream_readable.js:297:12)

2021-05-22T05:28:02.750970+00:00 app[web.1]:         at readableAddChunk (_stream_readable.js:272:9)

2021-05-22T05:28:02.750970+00:00 app[web.1]:         at TLSSocket.Readable.push (_stream_readable.js:213:10)

2021-05-22T05:28:02.775704+00:00 app[web.1]: Exiting...

2021-05-22T05:28:02.776495+00:00 app[web.1]: Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

2021-05-22T05:28:02.785798+00:00 app[web.1]: OK

2021-05-22T05:28:02.831273+00:00 heroku[web.1]: Process exited with status 0

2021-05-22T05:28:02.934913+00:00 heroku[web.1]: State changed from up to crashed


@chaoscreater
Copy link
Author

Can anyone help please?

@davidjameshowell
Copy link
Owner

@chaoscreater I just revisited this and I believe there was a fundamental flaw - you need to make sure that you are gathering the cookie from the /id endpoint as per this instruction

I was able to export my cookie from /id and successfully use it to login without needing to solve any captchas.

@chaoscreater
Copy link
Author

@chaoscreater I just revisited this and I believe there was a fundamental flaw - you need to make sure that you are gathering the cookie from the /id endpoint as per this instruction

I was able to export my cookie from /id and successfully use it to login without needing to solve any captchas.

I read in another thread that you do not need to use the cookies anymore, which should just use the username + password to login. This is what I'm using now (as per my screenshot). So do we still need cookies or not?

@davidjameshowell
Copy link
Owner

Yes, essentially cookies has been the only reliable method currently. I have since removed email/password from my config and have seen better results now.

I'd advise that cookie is the current best and most reliable method as of writing.

@chaoscreater
Copy link
Author

Yes, essentially cookies has been the only reliable method currently. I have since removed email/password from my config and have seen better results now.

I'd advise that cookie is the current best and most reliable method as of writing.

Thanks, will try that.

I'm currently using another project to claim free games and their method is slightly different, maybe worth checking out as well:
https://github.com/xMistt/DeviceAuthGenerator
https://github.com/Revadike/epicgames-freebies-claimer

@PandH4cker
Copy link

PandH4cker commented Aug 12, 2021

Hi everyone,

It's about 1 week that I just set up the jobs and that EpicGamesFreeNodeRun is well scheduled to run every 5 hours (for myself).

But, it doesn't seem to claim the games on the Epic Games Store, I reseted my cookie and added another one but same, it does not claim on the Epic Games Store.

I have configured Mailgun as per of the README, but no mails about potential Captchas resolution.

On Heroku, I don't see activity about the scheduled job (deploy activity or whatever), does this is normal ?

I don't know what am I doing wrong, if someone could help ?

EDIT: I Found that in Heroku logs:

2021-08-12T21:01:32.736148+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:01:32.736149+00:00 app[web.1]:     availableGames: []
2021-08-12T21:01:32.736986+00:00 app[web.1]: [2021-08-12 21:01:32.736 +0000] INFO  (19 on a5634a43-efbe-4b6d-9888-e2481709ca46): Unpurchased free games
2021-08-12T21:01:32.736988+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:01:32.736989+00:00 app[web.1]:     purchasableGames: []
2021-08-12T21:01:32.750500+00:00 app[web.1]: Exiting...
2021-08-12T21:01:32.751247+00:00 app[web.1]: Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
2021-08-12T21:01:32.754458+00:00 app[web.1]: OK
2021-08-12T21:01:32.827233+00:00 heroku[web.1]: Process exited with status 0
2021-08-12T21:01:32.984014+00:00 heroku[web.1]: State changed from up to crashed

It founds no free games but there are one new free game unclaimed.

EDIT 2: Finally the application is crashing:

2021-08-12T21:18:45.224967+00:00 app[web.1]: [2021-08-12 21:18:45.191 +0000] INFO  (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Checking free games for [email protected] 
2021-08-12T21:18:47.483974+00:00 app[web.1]: [2021-08-12 21:18:47.482 +0000] INFO  (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Successfully refreshed login
2021-08-12T21:18:47.483985+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:19:03.086365+00:00 app[web.1]: [2021-08-12 21:19:03.085 +0000] INFO  (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Available free games
2021-08-12T21:19:03.086375+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:19:03.086375+00:00 app[web.1]:     availableGames: [
2021-08-12T21:19:03.086375+00:00 app[web.1]:       "Rebel Galaxy"
2021-08-12T21:19:03.086376+00:00 app[web.1]:     ]
2021-08-12T21:19:04.371019+00:00 app[web.1]: [2021-08-12 21:19:04.370 +0000] INFO  (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Unpurchased free games
2021-08-12T21:19:04.371030+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:19:04.371030+00:00 app[web.1]:     purchasableGames: [
2021-08-12T21:19:04.371030+00:00 app[web.1]:       "Rebel Galaxy"
2021-08-12T21:19:04.371031+00:00 app[web.1]:     ]
2021-08-12T21:19:04.371645+00:00 app[web.1]: [2021-08-12 21:19:04.371 +0000] INFO  (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Purchasing Rebel Galaxy
2021-08-12T21:19:04.371645+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:19:06.081230+00:00 app[web.1]: [2021-08-12 21:19:06.080 +0000] ERROR (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): There was a problem processing your request.  Please try again later.
2021-08-12T21:19:06.081272+00:00 app[web.1]:     user: "[email protected]"
2021-08-12T21:19:06.116708+00:00 app[web.1]: [2021-08-12 21:19:06.082 +0000] ERROR (19 on 0c39abb0-4d3c-47d4-940e-ebdace236d43): Cannot read property 'map' of undefined
2021-08-12T21:19:06.116711+00:00 app[web.1]:     TypeError: Cannot read property 'map' of undefined
2021-08-12T21:19:06.116712+00:00 app[web.1]:         at Purchase.confirmOrder (/usr/app/src/purchase.ts:39:82)
2021-08-12T21:19:06.116713+00:00 app[web.1]:         at Purchase.purchase (/usr/app/src/purchase.ts:166:16)
2021-08-12T21:19:06.116713+00:00 app[web.1]:         at processTicksAndRejections (internal/process/task_queues.js:97:5)
2021-08-12T21:19:06.116714+00:00 app[web.1]:         at Purchase.purchaseGames (/usr/app/src/purchase.ts:174:7)
2021-08-12T21:19:06.116715+00:00 app[web.1]:         at /usr/app/src/index.ts:22:7
2021-08-12T21:19:06.116716+00:00 app[web.1]:         at async Promise.all (index 0)
2021-08-12T21:19:06.116716+00:00 app[web.1]:         at main (/usr/app/src/index.ts:31:3)
2021-08-12T21:19:06.165546+00:00 app[web.1]: Exiting...
2021-08-12T21:19:06.167559+00:00 app[web.1]: Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.
2021-08-12T21:19:06.185028+00:00 app[web.1]: OK
2021-08-12T21:19:06.260457+00:00 heroku[web.1]: Process exited with status 0
2021-08-12T21:19:06.370005+00:00 heroku[web.1]: State changed from up to crashed

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