Octonode Documentation
App troubleshooting
Diagnose preview, permission, build and project-loading failures.
| Symptom | Check |
|---|---|
| Unsafe plugin file in a Yarn workspace | Keep the generated installConfig.hoistingLimits: workspaces, reinstall, and rebuild |
| No granted projects | Review declared actions and consent; new projects are not automatically included |
| Hosted page cannot connect | Check frame-ancestors, X-Frame-Options, host reachability, and SDK initialization; retry in Studio |
| External tab expires | Reopen from Studio; standalone launch cannot receive parent renewal |
| Project list vanishes in a contribution | Use supported SDK nodes such as Section; arbitrary HTML lists are not serialized |
| One project fails | Preserve successful rows, show partial failure, and offer a safe read retry |
| Service failure is reported as authentication | Preserve AppRequestError.status; reserve 401 for invalid or expired sessions |
Keep authentication failure, denied access, no grants, partial failure, service failure and a genuinely empty result separate. Test a non-empty list in a browser, not only a mocked backend.
Before a release, run fresh generation, install, typecheck, build, artifact validation and a private installed-app test with two selected projects. Verify another project is denied, the page remains usable after session renewal, and revocation stops access. Use a permanent HTTPS release host.