After redirect, Google Play Store shows Open instead of Update

[kduvignau]

In my app, the update dialog shows up correctly, but after being redirected to Google Play Store, there is no Update button. When I click on Open, it opens my app again so I'm stuck.

If I open manually Google Play Store app and I go back to my app and click on update in dialog, then the Update button in Google Play Store is here.

Here is my code to check the app version:

  @override
  Widget build(BuildContext context) {
    // ...
    final newVersion = NewVersion();
    
    newVersion.getVersionStatus().then((versionStatus) {
      if (versionStatus != null && versionStatus.canUpdate) {
        newVersion.showUpdateDialog(
            dialogTitle: 'A new version is available',
            dialogText: 'Bla bla bla',
            updateButtonText: 'Update',
            context: context,
            versionStatus: versionStatus,
            allowDismissal: false);
      }
    });
    // ...

Here are the screenshots of the dialog and the Google Play Store page

Package version : ^0.2.3 App Id : com.app.journy

[timtraversy]

Hm - could you print the VersionStatus and post it here?

This might be related to you being a beta tester of the app. When I go to your public page (https://play.google.com/store/apps/details?id=com.app.journy) it says your version is 1.2.1, which is lower than 0.2.3.

This plugin only supports reading from the public Play store page, it can't check internal tests.

Bonne chance :)

[kduvignau]

Merci for you quick response!

This situation does not seem related to the fact of being a beta tester because it happened to other users that are not.

I should have been more precise my bad, ^0.2.3 is the version of new_version plugin that I use, My local version number was 1.2.0 and the one in Play Store was 1.2.1, I can try to reproduce it tomorrow and share the VersionStatus

Could it be possible that the plugin keeps a cache version of the play store page? Or maybe this happened because I tried to update the app right after a new release was rollout to production?

[wmfadel2]

Any updates on this issue?

[kduvignau]

The issue still occurs randomly, I'm not able to produce some useful logs though.

[adewaleafolabi]

I've also experienced this issue. In my case, while I was on the Play store, I had to uncheck the Enable auto-update option before I could see the update button.

It almost seems as if there's a rollout delay and what's available on the Play store might not be available to all users at the same time.

I also checked my app rollout policy and its set to be immediately available

[LostInDarkMath]

Yes, there is a roll-out delay