Troubleshooting

Version 1.0.0

Check the selected object, component, property and active filters before reporting a source that looks missing or stale. The steps below preserve your existing project data.

Select an object with an actual prefab relationship. Ordinary scene objects and unpacked prefabs do not have a prefab inheritance chain.

Clear search or disable Local overrides. The selected target may have no fields matching the active filters. Expand the property's parent group and choose a leaf field.

The object may have been deleted, unloaded or replaced. Unlock the window and select its current counterpart. The tool cannot recover a deleted source.

Press Refresh. Check that Component identifies the intended component and that the serialized path is correct. Multiple components of the same type appear separately. Third-party scripts that bypass Unity's change notifications may require a manual refresh.

Some custom inspectors do not forward Unity's serialized-property context menu. Open Window > Saphing Studio > Prefab Provenance and find the property in the tool instead.

1. Record the product version, Unity version and operating system.

2. State whether the target is an asset, variant, nested occurrence, scene instance or open Prefab Stage object.

3. Include the component, property path, observed source chain and expected result.

4. List the smallest set of reproduction steps.

5. Add a safe screenshot or minimal example without confidential or paid third-party assets.

Use product support to find the Discord forum and email contact. The forum is public. Do not post credentials, invoices or a complete confidential project.

Close the window. For an Asset Store import, delete Assets/SaphingStudio/PrefabProvenance. For a UPM installation, remove the package through Package Manager.

Included lighting assets are removed with the product folder. Generated examples live in a separate folder; keep or delete those independently. The tool does not attach product components to your scenes.