Troubleshooting
Recover without exposing your project.
Try the smallest safe recovery step first. Keep project paths, account details, tokens, and Handoff codes out of screenshots and reports.
Google sign-in does not return
- Leave the Meloft sign-in window open
- Finish in the system browser, not an embedded browser
- If the flow expired or was cancelled, return to Meloft and start a new sign-in
- Do not copy callback URLs or authorization codes into support messages
A Handoff link does not open Meloft
- Confirm Meloft is installed
- Use the complete canonical meloft.app/handoff link
- Choose Open Meloft on the bridge page
- If the code expired or was revoked, ask the sender to create a new Handoff
Project Doctor cannot read a project
- Confirm the source still exists and is readable
- If a ZIP contains several FLPs, select the intended candidate
- Retry after the project has finished saving
- Keep the original unchanged and review the structured error
A sample is missing
- Review whether the reference is external to the project folder
- Locate the asset yourself before preparing a package
- Do not treat a lower risk label as proof that the sample will travel
A plugin is Unknown
- Run Capability scan again
- Confirm the VST3 is installed in a standard or explicitly scanned root
- Unknown is intentionally conservative; it is not automatically Missing
An update fails
- Close active Meloft windows if the installer reports a file lock
- Open the Launcher again to retry
- Do not download an installer from an arbitrary R2 or third-party URL
Reset window state
Use the existing Settings window-state recovery control. This is separate from account, Project Library, and project data.