-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Start with:
bash scripts/verify.shIt detects missing tools, generated-project drift, formatting and lint errors, build failures, test failures, and invalid icon bundle metadata.
Command Line Tools alone cannot build Cadence:
export DEVELOPER_DIR="/Applications/Xcode.app/Contents/Developer"
xcodebuild -versionAdjust the path if the Xcode application has a different name.
brew bundleproject.yml is authoritative:
xcodegen generate --spec project.yml
git diff -- Cadence.xcodeprojCommit the generated project only when the source configuration changed.
Confirm that macOS allows Cadence to access the Music folder and that
~/Music is writable. Do not disable App Sandbox or add broad entitlements as
a workaround.
- verify the audio extension is supported;
- add the file or containing folder again;
- check the duplicate classification;
- keep an LRC beside its audio with a matching normalized basename.
Remember that Scan and Review do not copy files.
- inspect Audio Path in Now Playing;
- check the selected routing profile and output device;
- verify the managed file still exists;
- test built-in Mac output before Bluetooth, AirPlay, multichannel, or spatial routes.
The LRC needs valid line timestamps such as [01:23.45]. Plain text can be
displayed and edited but cannot follow playback.
Open Cadence Trash and use Restore. Empty Trash permanently removes managed copies and the restore manifest; it does not delete original imported files.
Open a focused GitHub issue with a synthetic reproduction. Remove personal media, metadata, paths, artwork, and lyrics. Use the private security route for vulnerabilities.