How does this package handle Android rollouts / internal testing?

[superplussed]

Hi guys, this package looks pretty amazing! I'm wondering how you guys handle Android rollouts? If I use 20% rollout as a default, is it just a 1/5 chance that your server will see the updated version? And is it possible that someone who is in a region that hasn't had the app rolled out to them yet will get a message that the app is available, when in fact it isn't available for them yet?

[tschoffelen]

Hi! That's a great question, to which I honestly don't know the right answer, as I personally haven't used phased rollouts on Android before.

The way this package grabs the version number of the latest version is by scraping the Google Play Store web page for the particular app. I'm guessing this will only show the new version number once it's live for all users, but I'm not 100% certain of that.

[DtheRock]

Hi,

What is happening when an app is not publicly available on google play, but on closed testing?

[tschoffelen]

This will scrape the public Google Play page to find the current version number, so closed testing versions will not be included in the response you get back.