Who is this article for?

Users who are updating to Vault Check Android app v1.0.27.

No special access or permissions are required.

A major update to the Vault Check Android app requires preparation to avoid data loss and ensure continued access. The latest version, v1.0.27, is being released at 21:00 on 20 May 2026.

This article explains the process in detail.

1. Requirements

As part of the update to the new app, Google may require the app cache for Check to be cleared on your device. This is a Google requirement and is outside of Ideagen's control.

Important

If the cache is cleared, any data that has not yet been synced to the server - including incomplete Checks and saved login information - will be permanently deleted from your device.

You need to take action to prepare for the release, to avoid possible data loss and ensure continued access to the app. The steps depend on your role.

2. Admin preparation

2.1 Identify users who sign in with a token

Vault Check supports two sign-in methods: username and password, or token and last name. For more information on these methods, see our article on accessing the Check mobile app.

To identify users who require new tokens, find all users in your organisation who use the token and last name method to sign in.

2.2. Generate new tokens ahead of the update

Generate a new login token for each user who signs in with a token before the release date and distribute the tokens to the relevant users.

Note

Users should not use their new token until after the updated app has been installed on their device - their existing token will continue to work until that point. Tokens expire 30 days after being generated. If a user does not sign in using the token within 30 days, you will need to generate another token for them.

2.3. Communicate the update to users

Notify your users of the update, directing them to the user section of this article so they can take the necessary steps before the update is applied.

2.4. Consider disabling automatic updates

If possible, consider temporarily pausing automatic app updates until users have had the opportunity to sync their data and receive their new tokens. This can be managed at the device level via the Google Play Store settings, or through Mobile Device Management (MDM) system settings if your organisation uses MDM.

3. User preparation

3.1. Complete and sync all assigned Checks

Before the update is installed on your device, make sure all in-progress or incomplete Checks have been completed and synced to the server, to avoid any data being lost.

You may need to perform a manual sync to do this.

3.2. Check how you sign in

Vault Check supports two sign-in methods: username and password, or token and last name. For more information, see our article on accessing the Check mobile app.

3.2.1. Username and password

If you sign in with a username and password, no special action is required. You will be able to log in as normal after the update.

To update the app:

1. Make sure you have completed and synced all assigned Checks as outlined in section 3.1 above.
2. Sign out of the app.
3. Install the updated app from the Google Play Store, if your organisation hasn't already installed it for you. The updated app is v1.0.27.
4. Sign in using your username and password.

3.2.2. Token and last name

If you sign in with a token and last name, your Administrator will have generated a new token for you ahead of the update.

To update the app:

1. Make sure you have completed and synced all assigned Checks as outlined in section 3.1 above.
2. Sign out of the app.
3. Make sure you have received your new token from your Administrator.
4. Install the updated app from the Google Play Store, if your organisation hasn't already installed it for you. The updated app is v1.0.27.
5. Sign in using your new token and your last name.