How to Fix Apex Legends Code:shoe (Out of Sync With Server)

By FixMyError · Updated October 16, 2026 · 8 min read

What Code:shoe means

Code:shoe is one of Apex Legends' most frustrating errors because of when it strikes. You are not sitting in a menu unable to connect — you are already in a match, maybe mid-fight, when the screen suddenly goes dark and you get an error reading "Out of sync with server (code:shoe)." You get bounced back to the lobby, the match is over for you, and in Ranked it can cost you RP or land you with an abandon penalty for something that was not your fault.

Under the hood, the error means exactly what it says: your game client and EA's servers have lost synchronization. Apex is a fast, precise game — your client and the server have to agree, dozens of times per second, on where everyone is and what is happening. When the two drift apart far enough, the server decides it cannot trust your client anymore and drops it. That drift can start on EA's side (an overloaded or glitching data center, especially right after a patch or during a limited-time event) or on yours (an unstable connection, packet loss, or a client that cannot keep up).

This is also why code:shoe behaves differently from Apex's other famous connection codes. Code:leaf shows up when the game cannot connect you to a match at all. Code:net appears when the server stops responding mid-game. Code:shoe is specifically the out-of-sync kick — you were connected and playing, and then the handshake between client and server broke down. The fixes below follow that logic: first rule out the server, then give yourself the most stable connection path, then make sure your client is not the weak link.

Common causes

• An overloaded or struggling EA data center: the classic code:shoe scenario — after an update or during a busy event, the data center you are connected to gets swamped and clients start desyncing.
• Unstable connection or packet loss: Wi-Fi dropouts, a congested home network, or ISP issues can interrupt the constant stream of sync packets between your client and the server.
• High Texture Streaming Budget overwhelming the GPU (PC): when the game streams high-detail textures on the fly faster than your graphics card can handle, the client can lag behind the server and trigger a desync.
• Corrupted or partially patched game files: a bad update or damaged files can leave your client slightly out of step with what the server expects.
• Background network load or an out-of-date client: downloads, streaming, or a VPN running while you play — or simply launching the game before an update has finished applying — can both destabilize the connection.

How to fix Code:shoe — step by step

Work through these in order. The first step saves you the most time: code:shoe is so often a server problem that you want to know that before you touch anything.

1. Check EA and Apex server status first Before changing anything, confirm the servers are healthy. Visit help.ea.com and look for the Apex Legends status, check the Apex Legends Status tracker, or search DownDetector for spike reports. Code:shoe often strikes right after an update or during a busy in-game event when a data center is overloaded — if thousands of players are reporting the same error at the same time, no local fix will help, and waiting is the only move.
2. Switch to a healthier data center On the title screen, press your platform's button to open the Data Center list (on PC it is the prompt at the bottom of the screen before you press continue). Pick a server with the lowest ping and 0% packet loss, even if it is not the closest one geographically. Leaving an overloaded or unstable data center is one of the most reliable fixes for code:shoe, and you can rejoin your preferred server once things calm down.
3. Lower the Texture Streaming Budget on PC On PC, open Apex Legends, go to Settings, select the Video tab, scroll to Advanced, and set Texture Streaming Budget to None. This reduces how much video memory the game uses to stream textures on the fly, which matters because code:shoe fires when the client falls out of sync with the server — an overwhelmed GPU pipeline is one way that happens. Restart the game after changing it.
4. Reset your local network Restart your router and modem, unplugging them for at least 30 seconds before powering back up. Use a wired Ethernet connection if you are on Wi-Fi. On PC, flush your DNS cache (open Command Prompt and type ipconfig /flushdns), then reset the network stack with netsh winsock reset and netsh int ip reset, and reboot. A stale or unstable connection is the most common player-side trigger for out-of-sync disconnects.
5. Repair game files and clear the client cache In the EA app or Steam, open Apex Legends' options and choose Repair to verify and fix corrupted files. If you use the EA app, also clear its cache (Settings, Downloads, Clear cache) and restart it. Launch Apex as administrator once (right-click the executable, Run as administrator) to rule out a permissions issue with the anti-cheat or network services.
6. Reinstall as a last resort If code:shoe keeps appearing after everything above, fully uninstall Apex Legends, restart your PC or console, then reinstall the game fresh. A corrupted or partially patched installation can cause repeat desyncs that no settings tweak will clear. While waiting for the reinstall, make sure your game is fully updated and that your system clock is set to automatic — a wrong date or time can also trigger sync errors.

Did this fix it? Quick checklist

• You can play full matches without the out-of-sync kick
• Your data center shows low ping and 0% packet loss
• Texture Streaming Budget is set to None on PC
• EA's status pages show Apex servers as healthy

If code:shoe keeps coming back, note when it happens — always after a patch, always on one data center, or always at the same time of day. That pattern tells you whether the problem is EA's servers (patch days, one bad data center) or your connection (evening congestion, a specific router behavior). You can also try a completely different network, like a mobile hotspot, for one session: if the error disappears, the problem lives in your home network setup. Reinstalling is the last step, not the first — most players fix code:shoe with a data-center switch or a network reset.