I've had to go through some serious contortions in order to test my billing code. Here's a list of complications that I've run into:
* There's no way for me to test subscriptions with my own account, because I can't buy from myself. As a result, I need a separate device with a separate account, using a separate credit card. * I couldn't find a way to debug my code, because billing requires a release build. * IabHelper doesn't detect cancelled subscriptions. Even after I cancel my subscription in Google Wallet, IabHelper reports it as "owned". So if I ever subscribe and want to go back to the unsubscribed state, I have to create another test subscription for my app. * Test subscriptions can't be deleted after they're activated, so the list keeps growing. * Managing subscriptions through the Google Wallet API is unintuitive. The UI doesn't show me the user login. The best I can do is to assume that I am the person in my zip code who purchased the subscription. * Changes to subscriptions take a while to propagate. Usually it's on the order of minutes, but the developer console says it can take hours. Is the process really as painful as I'm describing? I'd appreciate any suggestions to make billing development less painful. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
