I have an android app. It uses react-native-version-check to, when an updated version is available, display a modal and invite the user to go to Play Store and update the app on her device.
My problem is, sometimes (but not always), the library detects a new version, so I navigate the user to the storeUrl used by and returned by the library : https://play.google.com/store/apps/details?id=<APP_ID_GOES_HERE>&hl=en, but on the page the user only gets an "Open" button rather than an "Update" button.
I read about this post answer and checked. In my case :
- The app is built by a CircleCI workflow, using same process for subsequent builds
- The keystore used for signing the APK is the same for subsequent builds
- versionName is set as a concatenation of the date in YYYYMMDD format, plus the CircleCI build number, so the string obtained is always alphabetically greater than the previous one. This value is viewable on the Play Store page when I upload the APK, so it seems to be correctly set.
- versionCode is set as the CircleCI build number, so the integer obtained is always greater than the previous one. This value is also viewable on the Play Store page when I upload the APK, so it seems to be correctly set.
Is there another reason that could prevent from displaying the "Update" button ?
Thanks for any help
