Loading…
code:100 is an EA-services connection failure: the game couldn't complete the sign-in handshake with EA's account backend. Unlike code:net or code:leaf, it points at authentication — your account session, the platform's online service, or EA's login servers.
code:100 during an EA login outage is not fixable from your side. Also check PSN/Xbox Live status on console — Apex sign-in chains through the platform service, so their outage becomes your code:100.
On PC, sign out of the EA app entirely (not just close it), then sign back in and launch Apex. On console, sign out of your platform profile and back in. This forces a fresh auth token, which clears the majority of persistent code:100 cases.
Consoles especially: do a full power cycle, not rest mode. Cached network state survives rest mode and can keep a broken session alive.
TLS to EA's auth servers fails if your device clock is skewed. Set date/time to automatic and confirm the timezone is right.
Tethering to a phone hotspot for one login attempt is a fast way to split the problem: if code:100 disappears on the hotspot, the issue is your home network or ISP route to EA's auth endpoints, not your account.
The game couldn't complete a connection to EA's account servers during sign-in. It's an authentication-stage failure, usually caused by EA-side login problems, your platform's online service, or a stale local session.
Usually not — the overwhelming majority of code:100 reports are login-service problems. A banned account normally gets an explicit ban message. If code:100 persists for days while friends on your platform connect fine, check your EA account status and look your account up on a ban tracker.
Respawn doesn't publish an official meaning for most of these codes. These guides are written from community troubleshooting and the patterns we see across tracked accounts. Your progress through the steps is saved on this device.