Updates

How an update reaches a device

1. It is published

   A change is released to one channel at a time. Training first, so a change is used in a room before it is used at a border.

2. The app collects it

   Each app checks for a new version when it starts, and again while it is open. The download happens quietly in the background; nobody is interrupted and no screening is stopped.

3. It is applied when the app is put down

   The new version takes effect the next time the officer leaves the app — not in the middle of a screening. A half-entered record is never lost to an update.

4. A bad version undoes itself

   If an updated app fails to start, the device puts the previous version back on its own. A release that goes wrong does not leave a post unable to work.

The two channels

The screening app and the training app update separately and never mix. A version released for practice cannot land on a device recording real screenings.

What updates this way

Screens, wording, calculations, forms and fixes — which is nearly everything. A change to the device features the app uses, such as the camera or storage, still needs a new file from the download page. Those are rare, and you will be told when one is needed.

The browser version

There is nothing to update. Closing the tab and opening it again is enough; the current version is always the one that loads.

1. Close the app completely and open it again, with a working connection. That is when it looks for a new version.
2. Leave it open for a few minutes on a connection. It checks again while it is running.
3. Check the version shown inside the app against what your supervisor has been told to expect.

If it still has not moved, that is worth reporting rather than working around. Tell us, and say which app, which version and which post.