Forum Discussion

meowmeow0718's avatar
meowmeow0718
Newcomer
1 hour ago

EA login stuck on infinite loading spinner for a week

  • Launcher — EA app for Windows, version 13.827.2.6342. Steam appears only in the November 15 troubleshooting history.
  • Laptop — ASUS TUF Gaming F15 FX507VV4, BIOS FX507VV4.332
  • Windows — Windows 11 Home 22H2, 64-bit, build 22621.2428
  • Hardware — Intel Core i9-13900H, 16 GB DDR4-3200, 512 GB WD PC SN740 NVMe SSD
  • Graphics drivers — NVIDIA GeForce RTX 4060 Laptop GPU on 621.24 and Intel Iris Xe Graphics on 32.0.101.7092
  • Wi-Fi driver — Intel Wi-Fi 6 AX201 on 24.70.0.3
  • Game and anti-cheat — Apex build J30 / CL11734752 and EA Javelin Anticheat 1.0.16647165.0

3 Replies

  • Steps I performed

    • I launched Apex Legends through the EA app for Windows, version 13.827.2.6342. The game got past the intro, but the loading indicator kept spinning. Continue never appeared, and there was no error code.
    • I verified that the same EA account could reach the lobby on another PC using the EA app on the same home network. The other PC’s Apex build and driver versions were unavailable for comparison.
    • I switched the affected ASUS laptop from home Wi-Fi to a mobile hotspot. The EA app worked and launched Apex, but the game still spun before Continue. I then switched back to Wi-Fi.
    • I retested after EA app App Recovery cleared the cache. In a separate test, I manually signed out and signed back in to the same EA account. The spinner persisted in both tests.
    • I tested with ASUS LightingService (AURA Sync) temporarily stopped, without rebooting. The spinner persisted. The service was restored and verified as Running / Automatic.
    • I tested with the EA in-game overlay disabled, then separately with the NVIDIA overlay disabled. The spinner persisted in both tests. Both settings were restored.
    • I retested after using Repair for Xbox Game Bar in Windows Settings. Apex still spun, and GameBarFTServer.exe crashed again with 0xc0000005.
    • I retested after backing up the local Apex settings folder. Apex regenerated three configuration files that matched the originals byte for byte, so this test could not evaluate a clean default configuration. The original folder was restored.
    • I tested with the default Windows compatibility settings for EALauncher.exe and r5apex_dx12.exe. The spinner persisted. Both original settings were restored and verified.
    • I checked both the shared Javelin installer and the installer bundled with Apex. Neither offered a selectable Apex Legends entry. The manual reinstall was therefore not performed. The earlier EA app game Repair had completed and recorded exit code 0 for Apex’s Javelin installer.

    Comparisons and findings

    • November 11 versus November 12 — The last known working night and the first failing night recorded the same internal Javelin driver timestamp. Windows Update history showed no cumulative or feature update on either date. The Apex build at the time of the first failure is unknown.
    • November 15 temporary success — After my Steam launch failed, I switched to the EA app and briefly reached the lobby. The EA app copy started spinning again after I removed the Steam copy. Javelin logged Title is not installed. (apex) shortly after that removal. Windows then registered the service and loaded the driver. That specific error did not recur in recent failing launches.
    • Before and after the Javelin update — The spinner persisted after Javelin updated from 1.0.16556144.0 to 1.0.16647165.0. Windows recorded a successful Javelin driver load in the latest failing run.
    • Local sign-in traffic — Across three failing runs, the EA app returned matching, nonempty AuthCode responses for 20 of 20, 28 of 28, and 69 of 69 requests. The 69-request run followed a manual sign-out and sign-in on November 19, 2026, 13:39:45–13:44:58 UTC. Whether Apex redeemed the codes or established a game session remains unknown.
    • Network trace — In a separate failing run, Windows attributed 28 successful outbound TCP port 443 connections to r5apex_dx12.exe, along with one successful local connection to the EA app on port 3216. The trace recorded connection events and could not establish the game sign-in result.
    • Xbox Game Bar — The same GameBarFTServer.exe crash appeared before and after the brief November 15 success and during later failed launches. Its role in the Apex issue remains unconfirmed.

    The affected game build is J30 / CL11734752.

  • On Windows, the EA App version of Apex Legends is stuck on an infinite loading spinner before the "Continue" button appears. There is no error code displayed.

    • Cross-check: The same EA account can log in normally via the EA App on a different computer.
    • Affected System: Laptop running Windows 11 Home 22H2 (Build 22621.2428), EA App version 13.827.2.6342, Apex version J30 / CL11734752.
    • Troubleshooting already tried (issue persists): Repaired game files, cleared EA App cache, switched to a mobile hotspot, and manually logged out and back in.

    Technical Details (Logs):
    During the reproduction period from 2026-11-19 13:39:45 to 13:44:58 UTC:

    • The Javelin driver was successfully loaded.
    • The local SDK of the EA App successfully responded to all 69 login code requests.
    • (Optional: Despite this, the game client remains stuck on the loading screen.

    . The rest includes verified hardware and driver versions, the incident timeline, Windows event IDs, and the results of each troubleshooting test.

  • On Windows, the EA App version of Apex Legends is stuck on an infinite loading spinner before the "Continue" button appears. There is no error code displayed.

    • Cross-check: The same EA account can log in normally via the EA App on a different computer.
    • Affected System: Laptop running Windows 11 Home 22H2 (Build 22621.2428), EA App version 13.827.2.6342, Apex version J30 / CL11734752.
    • Troubleshooting already tried (issue persists): Repaired game files, cleared EA App cache, switched to a mobile hotspot, and manually logged out and back in.

    Technical Details (Logs):
    During the reproduction period from 2026-11-19 13:39:45 to 13:44:58 UTC:

    • The Javelin driver was successfully loaded.
    • The local SDK of the EA App successfully responded to all 69 login code requests.
    • (Optional: Despite this, the game client remains stuck on the loading screen.

    . The rest includes verified hardware and driver versions, the incident timeline, Windows event IDs, and the results of each troubleshooting test.

    Steps I performed

    • I launched Apex Legends through the EA app for Windows, version 13.827.2.6342. The game got past the intro, but the loading indicator kept spinning. Continue never appeared, and there was no error code.
    • I verified that the same EA account could reach the lobby on another PC using the EA app on the same home network. The other PC’s Apex build and driver versions were unavailable for comparison.
    • I switched the affected ASUS laptop from home Wi-Fi to a mobile hotspot. The EA app worked and launched Apex, but the game still spun before Continue. I then switched back to Wi-Fi.
    • I retested after EA app App Recovery cleared the cache. In a separate test, I manually signed out and signed back in to the same EA account. The spinner persisted in both tests.
    • I tested with ASUS LightingService (AURA Sync) temporarily stopped, without rebooting. The spinner persisted. The service was restored and verified as Running / Automatic.
    • I tested with the EA in-game overlay disabled, then separately with the NVIDIA overlay disabled. The spinner persisted in both tests. Both settings were restored.
    • I retested after using Repair for Xbox Game Bar in Windows Settings. Apex still spun, and GameBarFTServer.exe crashed again with 0xc0000005.
    • I retested after backing up the local Apex settings folder. Apex regenerated three configuration files that matched the originals byte for byte, so this test could not evaluate a clean default configuration. The original folder was restored.
    • I tested with the default Windows compatibility settings for EALauncher.exe and r5apex_dx12.exe. The spinner persisted. Both original settings were restored and verified.
    • I checked both the shared Javelin installer and the installer bundled with Apex. Neither offered a selectable Apex Legends entry. The manual reinstall was therefore not performed. The earlier EA app game Repair had completed and recorded exit code 0 for Apex’s Javelin installer.

    Comparisons and findings

    • November 11 versus November 12 — The last known working night and the first failing night recorded the same internal Javelin driver timestamp. Windows Update history showed no cumulative or feature update on either date. The Apex build at the time of the first failure is unknown.
    • November 15 temporary success — After my Steam launch failed, I switched to the EA app and briefly reached the lobby. The EA app copy started spinning again after I removed the Steam copy. Javelin logged Title is not installed. (apex) shortly after that removal. Windows then registered the service and loaded the driver. That specific error did not recur in recent failing launches.
    • Before and after the Javelin update — The spinner persisted after Javelin updated from 1.0.16556144.0 to 1.0.16647165.0. Windows recorded a successful Javelin driver load in the latest failing run.
    • Local sign-in traffic — Across three failing runs, the EA app returned matching, nonempty AuthCode responses for 20 of 20, 28 of 28, and 69 of 69 requests. The 69-request run followed a manual sign-out and sign-in on November 19, 2026, 13:39:45–13:44:58 UTC. Whether Apex redeemed the codes or established a game session remains unknown.
    • Network trace — In a separate failing run, Windows attributed 28 successful outbound TCP port 443 connections to r5apex_dx12.exe, along with one successful local connection to the EA app on port 3216. The trace recorded connection events and could not establish the game sign-in result.
    • Xbox Game Bar — The same GameBarFTServer.exe crash appeared before and after the brief November 15 success and during later failed launches. Its role in the Apex issue remains unconfirmed.

    Request for EA Support: Please check whether Apex received the sign-in or session initialization requests during November 19, 2026, 13:39:45–13:44:58 UTC, and whether those requests returned an error. The affected game build is J30 / CL11734752.

Featured Places

Node avatar for Apex Legends Technical Issues

Apex Legends Technical Issues

Having issues with Apex Legends? Join here to find help with connectivity, performance issues, crashes and more.Latest Activity: 8 minutes ago
42,600 Posts