> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launcherforge.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Common Errors

> Resolve common LauncherForge dashboard, CLI, upload, and game authentication problems.

# Common errors

## The CLI closes or returns to the menu after an error

Read the complete error message. Common causes include an expired session, missing permission, invalid folder, duplicate version, network failure, or workspace limits.

Restart the affected workflow after correcting the cause. Do not repeatedly retry without reading the reported error.

## My game does not appear in the CLI

Check that:

* The game belongs to the selected workspace.
* Your account has access to it.
* The game was saved successfully.
* The CLI session is using the expected account.
* The CLI is up to date.

Sign out and authenticate again when the session belongs to another account.

## The build folder is rejected

Select the packaged game root, not the Unreal or Unity project root.

The folder should include the final executable and runtime files. Avoid selecting source, intermediate, cache, or editor folders.

## The version already exists

Choose a new version following your version convention. Do not overwrite a published version unless LauncherForge explicitly supports that operation.

## The upload fails during transfer

* Keep the CLI and build folder open and unchanged.
* Verify the internet connection.
* Check storage and bandwidth limits.
* Retry after confirming the failed upload is no longer active.
* Review whether security software blocked the executable or network request.

## The game installs but does not launch

Verify:

* Executable path.
* Required runtime files.
* Working directory assumptions.
* Packaged dependencies.
* File permissions.
* Whether the executable was renamed after configuration.

## Authentication returns `valid: false`

* Start the game from LauncherForge, not directly from the executable.
* Confirm the `--launchToken` argument is present.
* Verify the validation endpoint uses the correct environment.
* Check whether the token expired.
* In Unreal Engine, keep the recommended startup delay.
* In Unity, use HTTPS in production.

## Shipping logs are not visible

Do not rely on console output as the only player-facing diagnostic. Add a safe authentication status or error screen that does not expose tokens or private data.