18

We are introducing Google Play subscriptions that include a 30 day trial, and I'm looking for some advice on how to test this.

As described in more detail here, the trial period for a testing account only lasts 3 minutes. Moreover, if an account (either a test account or not) has once received the free trial, they won't receive the free trial again. That means that every time that we want to test the onboarding and signup flow, we need to create a new Google account (add it to the group of accounts with license testing access, make it part of the group of testers that can download the app, opt-in for the internal test release and sign the new account in on the respective phone). This is tedious.

However, as I tried to create a new Google account for another round of testing, Google told me that my phone number (which is mandatory verification step) has been used too many times, and so I can't create any more accounts with this number.

I find it hard to believe that this is the only/the best way to test free trials with Google Play, so I'm happy with any help that can be offered on how to best approach this.

saltandpepper
  • 998
  • 2
  • 12
  • 32
  • Any solution on that? – thodwris Jul 04 '19 at 14:19
  • Unfortunately not. We've had to buy about 20 SIM cards in order to be able to create new accounts... – saltandpepper Jul 04 '19 at 16:31
  • Thanx for the answer. I followed your steps (add it to the group of accounts with license testing access, make it part of the group of testers that can download the app, opt-in for the internal test release and sign the new account in on the respective phone) but I get the following error from GPay "the item you were attempting to purchase could not be found". Do you have any idea? – thodwris Jul 04 '19 at 16:50
  • 1
    There are a number of reasons why this can happen. Make sure to read online and follow the many check lists that are out there (e.g. https://stackoverflow.com/questions/23918190/the-item-you-were-attempting-to-purchase-could-not-be-found-android-in-app-bil). In my personal experience the one step that often messes up my test flow is the step of opting in. When clicking on the opt-in link, make sure you're doing that with the right Google account. So for example, tap in the top right icon to check what account you're currently signed in to (in the browser you're opening the link with). – saltandpepper Jul 04 '19 at 16:56

2 Answers2

2

Umm, even if this is not a complete solution, it's rather an alternative to the main problem. It might be faster to just open another subscription from Google Play Console with free-trial enabled. You can subscribe to other free trials if the subscription ID is different from what you've activated the free trial with. That way you can use the same account but can activate free trial with different IDs.

You would also change the sku in the development section (remote or local, up to you.) It might take a while to get the information though, so I'd say open a bunch before start testing it next time.

The downside of this is, if anyone purchased a subscription, even if it's a test, it will not be possible to remove the test subscription, so be careful and be 100% sure to change your subscription IDs on production.

Furkan Yurdakul
  • 2,801
  • 1
  • 15
  • 37
  • Careful: there might be a limit on how many subscriptions Google Play allows. Deleting a subscription does not let you reuse the same ID so it may still count towards some limit. – mpartel May 17 '22 at 07:43
0

Include dev-environment-specific logic that treats specific users (or users having particular characteristics) as TRIAL-period users whose start date can also be finagled similarly. E.g., trial-2@mycompany.com could represent a user whose trial is 2-days old. This logic could be essentially inaccessible for apps in production.

David
  • 2,782
  • 4
  • 31
  • 47