Find the cause.
Keep the project safe.

The tool or welcome window is missing

The menu item is missing

1. Wait for Unity to finish importing and compiling.
2. Open Window → General → Console and fix the first compile error.
3. Confirm Assets/ScopeGarden/ReleasePreflight/Editor/ScopeGarden.ReleasePreflight.Editor.asmdef exists.
4. Confirm Unity 2022.3 or newer, then re-import the complete package if files are missing.

The welcome window did not open

It is skipped in batch mode and shown once per product version. Open Tools → Scope Garden → Welcome to Release Preflight.

Scene selection problems

No scenes appear in the sample

The sample copies enabled Build Settings scenes only. Enable scenes through File → Build Settings, choose Use enabled Build Settings scenes, or assign saved Scene Assets manually.

A scene becomes empty or reports “Missing scene”

Only saved Scene Assets inside the project are accepted. Save or restore the scene under Assets. When moving a scene, use the Unity Project window so its .meta relationship is preserved.

Duplicate or Build Settings warnings

Remove duplicates. If a selected scene is intentionally disabled, either enable it or document the reason it is inspected but not built.

Unity could not open a scene additively

Save open scenes, resolve import or compile errors and rerun. Check whether the scene is corrupt, belongs to an unsupported package or requires an unavailable dependency.

Missing scripts and slow scans

Missing scripts are reported

Open the affected scene or prefab and locate Missing (Mono Script). Restore the script and its .meta, replace the component or remove it only after confirming it is obsolete.

Scanning is slow

Replace the broad Assets folder with the smallest release-specific folders, such as Assets/Game/Prefabs and Assets/UI.

A folder is empty or ignored

Assign a valid Project folder inside Assets. External paths are unsupported. Remove blank rows and rerun.

Warnings look wrong

Confirm the active build target and inspect Project Settings → Player. Platform overrides can differ. Release Preflight reports the values Unity exposes in the current editor context; it does not switch targets or change values.

Results or exports are unavailable

Results disappeared

Changing a profile or any profile field intentionally invalidates old results. Run the preflight again.

Export buttons are disabled

Run a preflight first. Export is enabled only when at least one result exists.

The report does not open

The file is still written to the selected path. Open it from File Explorer or your editor and confirm that the folder is writable.

A report contains sensitive information

Do not share it. Project-relative filenames and folder structure can still be confidential. If an absolute path appears, keep the report private and submit a minimal reproduction.

The project fails after import

1. Confirm Unity 2022.3 or newer.
2. Fix the first Console error, not later cascading errors.
3. Check that no project assembly defines the same ScopeGarden.ReleasePreflight types.
4. Re-import the full package so scripts and assembly definitions remain together.
5. Try a clean project. If it works there, isolate assembly-definition or compiler conflicts in the original.

Batch-mode smoke test

Run Unity with the project path and:

-batchmode -quit -executeMethod ScopeGarden.ReleasePreflight.PreflightSmokeTests.RunBatchMode -logFile <log path>

A passing log contains RELEASE_PREFLIGHT_SMOKE_TESTS_PASSED and exits with code 0. Use the Unity version you intend to support.

Reset profiles safely

Profiles live at ProjectSettings/ScopeGardenReleasePreflight.asset. Commit or copy it first. Remove it only while Unity is closed, then reopen the project to create a new default profile. The welcome window can always be opened manually; no preference reset is required.

Before contacting support

• Save scenes and clear unrelated Console errors.
• Record Unity version, OS, product version and exact steps.
• Try the same steps in a clean project.
• Include only project-relative paths and a minimal non-confidential sample.
• Never send passwords, API keys, customer data or a proprietary project archive.