Solve common problems
These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.
Start by identifying whether the problem affects editing, saved data, generated output or an external service. Keep the original project and a .modo copy while investigating.
| Symptom | Check first |
|---|---|
| A Hug frame collapses around its text | The parent needs an appropriate Stack/Grid layout; the child should be In flow to contribute to its size |
| Fill width stops before the frame edge | Parent padding, nested containers, min/max constraints, alignment and an active breakpoint override |
| Gap does nothing | Only children participating in layout contribute; check Absolute positioning |
| A change appears only on Mobile | The active frame is a secondary breakpoint; reset its override if you want inheritance |
| App colors do not match project colors | Application Appearance and project light/dark mode are separate settings |
| A video or animation is still on the canvas | Editing keeps media paused; test it in Preview |
| A font is missing offline | Download/import its required files before disconnecting; check the selected weight and style |
| A layer is hard to find | Double-click its icon in Layers to focus it; double-click the name to rename |
| CMS edits do not appear on a published site | Local Published state does not redeploy the site; export/publish again |
| A cloud version is not on another device | “Saved to folder” confirms a local write; inspect the provider's sync status |
| MCP is enabled but not lit | Make a successful context request and inspect Connections |
| A publish or GitHub plan cannot be confirmed | The project, destination or remote revision may have changed; prepare and review a new plan |
Saving and recovery
Finish editing the field and wait for Saved locally before quitting. If a save error is shown, retry and preserve a portable copy if available. A save indicator must not be treated as successful while an error is still active.
Reopening a previously opened .modo archive can resume its managed working copy, including later edits. It is not automatically a request to roll back to the older archive bytes. Read saving and recovery before attempting a restore.
Do not delete the app profile, recovery folder or original project to “reset” a saving problem. Export what you can and report the issue.
Warnings and output
Open the warning details to identify the affected layer and target. Some warnings describe a portability limitation; others block export. Do not infer the cause from the count alone.
Compare Preview with the generated output when reporting a rendering difference. Include the target, breakpoint, theme, relevant font/media and smallest project that reproduces the issue.
Installation and account problems
Check About this build and distinguish MODO from personal Preview or QA builds. The alpha's real activation service, distribution signature and email delivery have separate release checks. A passing local test suite is not proof that an unreleased installer can activate another person's email.
See installation and access. Windows and the latest Linux beta access flow still need their respective platform verification.
Need a correction? Tell us