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

EGS login fails with complex password #48

Open
LoneBoco opened this issue Jun 11, 2024 · 1 comment
Open

EGS login fails with complex password #48

LoneBoco opened this issue Jun 11, 2024 · 1 comment
Labels
third-party issue This is a third-party issue, not related to Junk-Store code

Comments

@LoneBoco
Copy link

Describe the bug
You are unable to log into your EGS account if your password contains special characters. I had a 32-digit password with the special characters ,&#"; and a TOTP 2FA set on my account. I went through the login process like normal and it claimed I logged in, but I would not see any of my games on my account.

I went to the logs and looked at my epiclogin.log and saw this:

** (process:12198): WARNING **: 00:16:35.889: Error writing credentials to socket: Error sending message: Broken pipe

I've had issues with 3rd party services before where a complicated password isn't sent correctly, so I tried changing my password to a 20 character alphanumeric password to check. I went through the whole process again and this time I was able to see my games; the error went away. It does seem to indicate an issue encoding the password.

To Reproduce
Steps to reproduce the behavior:

  1. Set a password on your EGS account that has a bunch of special characters.
  2. Try to log into your account.
  3. ???
  4. You are logged in but have no games.

Expected behavior
I expected to be able to log in and see my games.

Handheld device (please complete the following information):

  • Device: Steam Deck
  • OS: SteamOS
  • Version: 3.5.19 (stable)
@ebenbruyns
Copy link
Owner

I think you should log this issue on the legendary repo instead. I don't maintain legendary where this issue occurs. I'll leave this open for the mean time because I might have to patch it if it doesn't get fixed.

That's some good bug hunting though!

@mrsjunkrunner mrsjunkrunner added the third-party issue This is a third-party issue, not related to Junk-Store code label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
third-party issue This is a third-party issue, not related to Junk-Store code
Projects
None yet
Development

No branches or pull requests

3 participants