Here’s another solution I have that also relates to what @vancewong mentioned.
I solved this issue by adding a new collection to my Adalo app named, “Latest App Version.” Every time I submit a new version either to the App Store and/or Google Play Store, I input one similar build version in a number field in the collection.
Here’s a more detailed example:
Here’s the collection with a single number property named
Latest App Version. It’s up to you, the developer, to add your app’s latest build version. Even if your TestFlight and Android build has different versions, find a similarity, as it is not currently possible for your app/Adalo to differentiate different OS and check for two different versions.
When a user logs in, you can have the default screen that a user sees when they log in/open the app have an action to update the user’s current version. Essentially, make sure you have a new number property in you user collection called “Current App Version.” You’ll need to manually change this version number before publishing a new build for your app. Don’t forget!
Now that you have the structure. Let’s move forward with how you can have a prompt pop up whenever a user’s current version does not match the latest version you have set. On my main home screen for my app, users can receive either a non-intrusive or intrusive banner that lets them know they need to update their app. It’s set to only appear if a user’s current app version is LESS THAN the MAXIMUM latest app version. So that way, you don’t have to delete the last build version you put in the
Latest App Version collection before putting a new version. Just make sure you don’t put new build version that is less than the last one you entered.
Alright, let’s recap.
You’ve created the following from the start:
- A new
Latest App Version collection, where you’ll input one single new version for both TestFlight and Android builds.
- A new number property for your
Users collection named “Current App Version.”
- Your default home screen has an action that will update a logged in user’s
Current App Version number property with something that you’ve manually inputted (usually the same latest app version # that you’ve put in the
Latest App Version collection.
- A new screen, modal pop-up, or banner that appears when a user’s current app version is less than the maximum latest app version.
5. You make sure to change the maximum latest app version when your TestFlight build is Ready For Sale on the App Store and/or your Android build has reached public production, so that users will know that it is time to update. Doing this beforehand will prompt users to update and they wouldn’t be able to do so if your new app version isn’t available to publicly download, obviously.
Practice makes perfect with this as sometimes you might forget to change your home screen’s current app version update action before publishing a new build. If you are need in more assistance with this, let me know. I’m happy to help! This might seem like a lot, but I promise it’s not that bad at all.