Error Code 1000 When Logging in With Oculus/Meta

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.

Hello, can you upload a full set of logs? Can you also give us a rough percentage of players who encounter this issue and if the issue is 100% reproducible for them?

Thanks for the logs! Can you answer the following questions:

  1. Are you accessing EOS SDK APIs over multiple threads?
  2. Do you know if players encountering this issue are connected to a network with a restrictive firewall? If they can test on a different network that would be really helpful.

Yeah the request is making it’s way through, and our backend is returning a 500 (server error). I was wondering if there was something at the network level causing our server to error out.

I’m not sure why my log search didn’t turn up anything yesterday, but I found a useful log message on our backend this morning:

EOS user already exists for identityProviderId: oculus_app_id

Does your game call EOS_Connect_LinkAccount? I’m trying to pinpoint when this server error would be thrown. We should also return a better error than a 500 in this case.

Thanks for the info. I reached out to our backend team for some help. Given the limited number of players affected it might take a bit of time for me to get back to you. If the urgency increases here, please let me know!

Yes, happens 100% of the time to the people affected by it. Very small percentage from what we can tell.

Full log attached here.

  1. Not accessing over multiple threads, no.
  2. When I asked the player if they had any extreme network security they told me no. I’ll ask if they can try on another network. Out of curiosity if the API is able to return the error presumably they were able to make the initial request. What should we be looking for from that side?

We’re using EOS_Connect_Login, via FUserManagerEOS::ConnectLoginNoEAS in UE5.4.

I also had the player test a build using 5.5 and the new login flow, but the same result. EOS_Connect_Login also used in that situation.