-
-
Notifications
You must be signed in to change notification settings - Fork 450
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
Heroic logged me out of Epic with no way to log back in #4289
Comments
Hi also facing this issue, I was also logged out then tried to log in to the wrong account and am now stuck with this same error. How can we clear the cache/session storage of the Heroic browser? The Clear Cache button and the Reset Heroic button have both been tried but the browser is still stuck on that error URL whenever I try to log in now. |
Just got this today. There is a new privacy policy, in addition to the recent new EULA, that needs to be accepted. Login into your account on the web browser and accept the new privacy policy. Then a few minutes later you will be able to get a new authorization code. I had to use the alternate method and paste the authorization code from the web browser a few minutes after accepting the new privacy policy (I also had to disable IPv6 to get it to add the account again). |
So this worked? Although the alternative method gave me an instant error, just clicking on Login with Epic logged me in instantly. |
After accepting the privacy policy via the store page I got logged out of Epic on next Heroic load. Clicking the normal Epic login twice worked and I've stayed logged in since. |
steam deck user here..
|
Worked for me. Whichever gets you back in is fine. Either way, the issue is the need to accept the new privacy policy before we can login from Heroic again. |
Agreed. Worked for me. |
How exactly do i except the eulea from the brower |
So, i just managed to accept the new EULA by going to Stores > Epic Store in Heroic Game Launcher, it prompted me to log in like 2-3 times, but after that it showed me the new EULA. Hope this helps someone.... |
I encountered this issue too. You need to log in on epicgames.com in your browser and accept the new EULA. Then you can log in with Heroic as normal. |
That worked for me. Thanks mate! |
Hey I see that this is unverified but I am having this issue with my epic games account I was going to play some subnautica but the game won't launch I restarted the client and I was logged out I tried to log back in but all that I got was this
Note: resetting your epic games account password fixes the issue for some reason I did this when I first got the client because I didn't update the password for my account yet but now it's happening again and I would rather not reset my password again |
Thank you this fixed my issue |
Yes, Fixes the issue. |
Can confirm. Worked on first try. Oh, the things we do for convenience. |
You actually don't need to open the epic games launcher you can just go to epicgames.com and accept it there |
Same. |
Also having this issue. |
@ArchUser02 @Apollonu |
Just open your normal browser and accept the agreement then re-open Heroic . Worked for me |
Just go to epic (in whatever browser you are using to link), then accept the updated privacy policy, and voila! Your soul is forked over to the devil. |
Describe the bug
I tried to open one of my games from Epic games from Heroic through Steam, and it didn't open, so I opened Heroic to see that I have been logged out. Upon pressing Epic Games login it gives me this error:
"errorCode": "errors.com.epicgames.oauth.corrective_action_required",
"message": "Corrective action is required to continue.",
"metadata": {
"correctiveAction": "PRIVACY_POLICY_ACCEPTANCE",
"continuation": "ed96f9586c3d4b7bb5267415b5f7338b"
},
"correlationId": "4071d020-d52d-11ef-9b44-efa2b9da6785"
}
(Trying to log through the alternative method yields the exact same result)
Add logs
Steps to reproduce
Expected behavior
It should give me the option to login with an Epic Games account
Screenshots
Heroic Version
Latest Stable (Flatpak)
System Information
Additional information
No response
The text was updated successfully, but these errors were encountered: