frameDockDocumentation

Recover from setup and build blockers

Read the failed check, resolve its cause and retry safely.

The sign-in request expired

Choose Try again in the application and request a fresh link. Keep the application open, compare the new code with the code in the email, then approve that request. Do not reuse the expired link or approve a request whose code does not match.

Application example: the sign-in request expired.
Application example: the sign-in request expired.
Application example: the sign-in request expired.

Application example: the sign-in request expired.

The project is not detected

Select the folder containing the engine’s project file, not a parent workspace or a built executable. For repositories, confirm the project subfolder and current read permissions.

The selected editor is incompatible

Check the version named by the project. Choose a compatible installation or resolve the correct version through the supported vendor path. Do not silently upgrade the project to fit a different editor.

Application example: the selected editor is incompatible.
Application example: the selected editor is incompatible.
Application example: the selected editor is incompatible.

Application example: the selected editor is incompatible.

Templates, modules or native tools are missing

Read the failing target environment row. Godot needs matching export templates; Unity needs the selected native target module/backend and a valid license. Unreal needs matching C++ tools and SDK: Visual Studio and the Windows SDK on Windows, or the engine-compatible compiler and SDK on Linux. Resolve the named requirement, then Recheck.

An account is detected but access is not verified

Confirm the intended provider account and its current project permissions. Configuration and verified authorization are distinct. Local builds can continue without optional publisher connections.

A setup operation was canceled or interrupted

Use its retained status, error and recovery controls. Recheck the environment before retrying. An abrupt interruption recovers as interrupted; a normal shutdown cancels active setup operations.

The build failed

Open the original engine log and find the first actionable error. Confirm the target and configuration, resolve the cause, then retry. A canceled run is not a successful artifact.

Application example: the build failed.
Application example: the build failed.
Application example: the build failed.

Application example: the build failed.

The extracted game does not launch

Check that all manifest files were extracted, required runtime dependencies are present and the configuration is intended for distribution. Rebuild after project corrections.

A download or account feature is unavailable

Check the package checksum before installing. If no package is listed for your computer, review its platform requirements. Downloads do not require an account. The desktop app requires a free frameDock account; a valid signed session works offline until its lease expires.