Troubleshooting

Troubleshooting

If something is broken, the fastest path is:

1. Open Settings.
2. Click Logs at the bottom of the sidebar.
3. Review app.log or app.previous.log, then attach the relevant file to a GitHub issue with a short description.

The logs contain only what accshift itself printed (timestamps, error messages, redacted account ids). No passwords, no full account names.

The rest of this page lists the most common symptoms by platform.

Steam

Switching does nothing or signs in as the old account. Steam must be fully killed before the relaunch reads the registry. accshift kills steam / steam.exe and the web helper, then waits for them to exit. If you have a stuck Steam process (frozen UI, hung overlay), kill it manually and retry.

"Steam installation not found". Set the path override in Settings > Steam. Point at the directory that contains config/loginusers.vdf.

Linux Flatpak or Snap: nothing happens on switch. Flatpak is launched through flatpak run com.valvesoftware.Steam; verify that the flatpak command and app id are available. Snap is launched through the steam wrapper; verify that it is on PATH. The path override must still point to the data directory containing config/loginusers.vdf, not to the launcher executable.

Ban check returns nothing. Set a Steam Web API key under Settings > Steam. Without one, ban and profile lookups are disabled.

Riot Games

Switching does nothing. The Riot Client requires Stay signed in to be checked when the session was captured. If it was not, the tokens are short-lived. Sign in normally, check the box, and use Capture Session from the right-click menu.

"Riot Client not found". Set the path override in Settings > Riot Games.

Battle.net

Battle.net opens on the wrong account. Confirm Battle.net is fully closed before the switch. The reorder only takes effect on a cold start.

Epic Games / Ubisoft Connect

Switch lands on the previous account. Same root cause as Battle.net: the launcher must be fully closed for the snapshot restore to take effect. Kill any hung launcher process manually and retry.

Roblox

"Cookie no longer valid". Roblox invalidates cookies on sign-out elsewhere or on long inactivity. Recapture via Quick Login, or paste a fresh .ROBLOSECURITY cookie under Settings > Roblox.

Studio still uses the old account. Switch via accshift, then restart Studio. The cookie is written to the registry on switch; Studio reads it on launch.

CLI

exit code 4: lock_contended. Another accshift process (GUI or CLI) holds the exclusive mutating lock. Wait for it to finish, then retry. The lock timeout is 2 seconds.

exit code 2: PLATFORM_UNAVAILABLE. That platform is not compiled into this build, usually because the host OS does not support it (e.g. Riot on Linux). Run accshift platforms to see what is actually available.

Output looks like JSON instead of a table. Stdout was detected as piped or redirected. Run in a TTY for the table form, or pass --json explicitly to lock the format.

PIN lock

Locked out after too many failed attempts. There is a short delay between attempts on failure, not a permanent lockout. Wait a few seconds and retry. If the PIN is genuinely lost, delete the user/ directory under the per-OS data path (see Security) to reset it. This wipes other UI settings too.

macOS install

"Accshift is damaged and can't be opened" or unidentified-developer warning. The dmg is not signed yet, so Gatekeeper quarantines it on download. Clear the flag once and reopen:

xattr -cr /Applications/Accshift.app

Linux folder picker

Path override picker does not open. accshift shells out to zenity or kdialog. Install one of them, or type the path manually into the input field.

Secrets

"keyring: ..." errors on Linux or macOS. The OS keyring is not running or not unlocked. On Linux start gnome-keyring-daemon or your session's equivalent. On macOS, the Keychain prompts for permission the first time it is touched; allow access.

Logs

Logs live under:

• Windows: %APPDATA%\com.accshift.desktop\logs\
• Linux: ~/.config/com.accshift.desktop/logs/
• macOS: ~/Library/Application Support/com.accshift.desktop/logs/

Use the Logs button at the bottom of Settings to open the folder. Review the relevant file, then attach it manually to a GitHub issue.