I’m integrating Epic Online Services SDK 1.19.2.1 into a Windows Unity 2022.3 IL2CPP game mod using C# and BepInEx 6.
The SDK initializes successfully, and PlatformInterface.Create() returns a valid platform instance.
However, when calling Connect.CreateDeviceId(), authentication fails with:
HttpStatus: 401
ErrorCode: errors.com.epicgames.eos.auth.client_not_found
NumericErrorCode: 110002
ErrorMessage: Client not found
Result: EOS_InvalidCredentials
I’ve verified that the Client ID, Product ID, Sandbox ID, and Deployment ID match the values displayed in the EOS Developer Portal.
My configuration includes:
-
A client assigned to a Peer2Peer client policy
-
An active public Live deployment
-
EOS SDK version 1.19.2.1
-
Windows 10 x64
The EOS SDK reports that the network is online and successfully updates its platform configuration, but it cannot obtain a client authentication token.
My questions:
-
What could cause
client_not_found (110002)when the Client ID matches the Developer Portal? -
Are newly created EOS clients subject to an activation or propagation delay?
-
Is there an additional configuration or entitlement required before the EOS backend recognizes a client?
Any guidance would be appreciated.