Package and publish
Ship the tested result to the intended destination.
Reviewed 6 October 2026 · 2 min read
Import example project ↗Two named conversations, shared files, revisions and a preview.
Before you start
Publishing is separate from previewing/building. Identify destination and account, and make distribution part of the request.
Signing, memberships, hosting and licenses can require external setup. A local build does not satisfy those requirements.
Step by step
- Run relevant final checks and record source/build version.
- Produce the platform package or production website build.
- Verify signing, configuration and account access.
- Publish through the intended channel.
- Download/open it as a new user and test the main flow.
Try this
Example request
Prepare this app for release. List tests and signing checks, build it and verify the installed result. Publish to the agreed destination only when those checks pass; report remaining external setup.
Check the result
- The public artifact matches the tested build.
- Links work signed out and off the private network.
- Upgrade/recovery behavior is checked.
- Prepared/uploaded does not mean published.
If something goes wrong
Inspect certificates and local key access for signing failures rather than disabling checks.
Keep the last working deployment while diagnosing a failed new build.
Your screen may differ by platform and version. Check availability or get help.