Question: Does react-native-check-version handle staged Play Store releases correctly?

[rohith-thummanapally-sidsfarm]

Hi team ,

I have a question regarding staged rollouts on Stores.

Scenario

We’re using staged rollout for our app updates (for example, releasing to 5% of users first). Devices included in the 5% rollout saw the newer version. Devices not yet in the rollout still saw the old version.

Question

Can you please confirm whether react-native-check-version behaves correctly during staged rollouts?

Specifically:

Does it fetch version info in a rollout-sensitive way (depending on whether the user’s device/account has access to the update)?

Or does it always return the latest version from the Stores globally (regardless of rollout stage)?

If you have any technical insight into how the library queries Stores data (e.g., scraping HTML, Play Services API, etc.), that would also help clarify.

We want to avoid false update prompts for users who have not yet received the staged release update.

[tschoffelen]

Please see #14. The package scrapes the HTML of the Google Play page, but I am not entirely sure whether that means it correctly picks up stages roll-outs, because I'm not sure whether that HTML will reflect the rollout status for the current device.

My thinking would be that it probably doesn't out of the box, so I would recommend doing some time logic with the updateAt date returned (e.g. only showing a modal to the user if the update was released more than X days ago, if you know that's usually when you complete the rollout).