We’ve run into a few players who have never been able to login to EOS through our game, always receiving UnexpectedError. I was able to have one of them provide me with logs recently and this is what EOS is returning when the player in question is logging in. Is there anything we can do to debug this issue with this player?
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320: request has been successfully processed. URL: https://api.epicgames.dev/auth/v1/oauth/token, HTTP code: 500, content length: 176, actual payload size: 176, elapsed: 0.39s
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header Date: Sun, 16 Feb 2025 23:28:28 GMT
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header Content-Type: application/json
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header Content-Length: 176
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header Connection: keep-alive
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header X-Epic-Correlation-Id: EOS-IWT8AlBMSc8-BECFyNDAhg-SgkT3vJC5Yd0JvSkYyeAgQ
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header X-Epic-Error-Code: 1000
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header X-Epic-Error-Name: errors.com.epicgames.server_error
[2025.02.16-23.28.28:495][ 63]LogEOSSDK: Warning: LogHttp: 0x72d99a2320 Response Header Server: eos-gateway
[2025.02.16-23.28.28:496][ 63]LogEOSSDK: Warning: LogEOS: Error response received from backend. ServiceName=[EOSAuth], OperationName=[TokenGrant], Url=[<Redacted>], HttpStatus=[500], ErrorCode=[errors.com.epicgames.server_error], NumericErrorCode=[1000], ErrorMessage=[Server Error], CorrId=[EOS-IWT8AlBMSc8-BECFyNDAhg-SgkT3vJC5Yd0JvSkYyeAgQ]
I was able to confirm that Meta is providing them with a NOnce and that that is being passed to EOS in the format expected.