Identify the failing layer
Heroic is a front end to multiple store and launcher components; Epic-related authentication can involve Legendary, embedded web views and token state. GOG downloads and DLC metadata follow other paths. A login loop does not by itself identify a Wine graphics problem and should not be 'fixed' by clearing the game prefix. First record the store, Heroic package type, authentication stage and whether the game actually reaches its Windows launcher.
Collect discriminating evidence
Heroic's project troubleshooting guide documents separate configuration and Legendary paths, including different locations for Flatpak. Read the built-in launcher log rather than publishing token files or the entire configuration directory. Compare a store login failure against a game-only launch failure and identify recent Heroic, Legendary or provider changes. When a game requires an additional Ubisoft or EA login, each provider has independent online state and can fail after Heroic succeeds.
Compare safely and record limitations
Use the same account and game with only one change to package version, network context or selected runner if supported. Do not disable TLS verification, paste authentication codes into unknown helper scripts or rename folders containing credentials as a first step. For games using Proton outside Steam, check whether Heroic is using an appropriate umu-backed path. A successful store sign-in proves only the authentication step, not DXVK compatibility, anti-cheat access or server-side game availability.
Gather evidence before changing the system
Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.
Read-only observation
flatpak list --appRequirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.
Identify whether a Flatpak Heroic sandbox is in use before comparing config locations.
Read-only observation
date -IsRequirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.
Record host time for correlating login error timestamps; never expose authentication tokens.
A controlled test with a way back
Preserve launcher logs with tokens redacted; compare one official Heroic login flow with the same store account before changing the Wine prefix.
Rollback: Revert only the package or runner change; retain existing account configuration.
What this test cannot establish: Provider authentication can change server-side; a historical success is not a current guarantee.
Sources and scope
This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.
- Heroic official troubleshooting
Heroic separates launcher configuration from Legendary and its authentication state.
- umu-launcher documented workflow
umu supplies an external-client Proton runtime rather than implying Steam compatibility.