Update the app with a new version

Last updated

When you have a newer .zip, you replace what's running. Your link stays the same.

Do it

  1. Open the app's page
  2. Upload the new zip through the same flow you used the first time
  3. Wait for it to build and start
  4. Open the link and check it works

Your settings — the values you were asked for, any storage attached — carry over. You're replacing the code, not the configuration.

What to expect

  • A short interruption. The old version stops before the new one starts. It's brief, but if people are using the app, a quiet moment is a kinder time to do it.
  • The same link. Nothing you've shared stops working.
  • Anything not in storage is reset. If the app keeps files and doesn't have a volume attached, an update wipes them — see Things worth knowing. This is the one to ask your developer about before updating, not after.

Check afterwards

Same as the first deploy: open it and use it. A green status means the new version started, not that it's correct.

If something's wrong, the fastest fix is usually to ask for a corrected zip and update again — the process is quick and repeatable, and there's no limit on trying twice.

If the new version is broken

Copy the Logs and send them to whoever built it. Mention that it worked before the update, which immediately narrows things down for them.

If the app is important and the new version doesn't work, ask whether they can send you the previous zip to upload while they fix it. Going back is the same process as going forward.

Keep the old zips

Worth saying because it's cheap and people don't: keep the zip files you've been sent, with dates in the filenames. If an update goes wrong, having last week's version on your own machine turns a problem into a five-minute fix — and it doesn't depend on anyone else being available.