Updating and reporting problems

Before updating

1. Read the release notes for supported platforms and migration steps.
2. Save project changes and make a backup of important work.
3. Stop active tasks cleanly before replacing the desktop app.
4. Update the client when the release requires a matching version.
5. Retest a project locally, then on the phone.

Use the release channel that supplied your build. These guides do not promise an automatic updater or a rollback path for every early-access package.

Write a reproducible report

Desktop version and operating system:
Client version and device:
Project type (for example, Vite or Next.js):
Connection: same network / different network
Steps to reproduce:
Expected result:
Actual result and visible diagnostic code:

Remove credentials, connection codes, personal file paths, and private project content. Include a small reproducible example when possible. Start with troubleshooting to narrow the failing step.

Check the release boundary

Early access and full V1 have different gates. Accounts, billing, remote wake, broader extension execution, and additional platforms have their own acceptance work. Follow release status rather than assuming an upstream feature is included in the Lyre build.