-
-
Notifications
You must be signed in to change notification settings - Fork 474
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
fix: use egs's flow for epic login #4379
fix: use egs's flow for epic login #4379
Conversation
262d2ec
to
47f8a22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works as expected and way more simple than before
const userAgent = | ||
startUrl === epicLoginUrl | ||
? 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) EpicGamesLauncher' | ||
: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/200.0 HeroicGamesLauncher' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, maybe we don't need those double UA tbh, I only added this one to try to fix some issues with random errors on epic login, server errors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking it may be worth keeping for some browser side loaded apps. Or in the future let users configure user agent strings for browser apps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good stuff with this refactor
Instead of routing through legendary.gl/epiclogin we will call different url directly, this should prevent any issues with corrective actions etc..
I have also modified our useragent to contain mention about Heroic
Use the following Checklist if you have changed something on the Backend or Frontend: