Google Play IAP Won't call back if user fails to enter passward

I was doing some testing on Google Play’s IAP and ran into a serious problem where the IAP be stuck, and the code won’t call back. I want to see if this is a bug I should be reporting, if others have found a better way around it. Steps to create the problem:

1 - Call

       store.purchase({productID});

       native.setActivityIndicator( true );

2 - Google pops up a purchase screen, hit “Buy”. Then if you haven’t made a purchase before, it will give you a password screen (see screen 1). Enter a wrong password, and you get screen 2.

3 - At this point, there is no way for the user to “cancel” the purchase. You are completely stuck. There is no way for you to close the screen (tapping in the black space behind the dialog box won’t close the dialog box like the previous screen). Also since there is the activity indicator in place, there is no way for me to capture a touch. Even if I could, there is no API call for me to “cancel” the purchase and close that screen 2. To make things worse, if the user were to touch the “forgot password” link, the user will leave my app. When the user comes back, all the user would see is the activity indicator. At no point would I get a callback that indicates the purchase has failed or is cancelled.

Has anyone else seen this, seems like a very serious problem!

Andrew

 

OK. I did some more testing and realized that as long as the user stays within the app, the user can still hit the back button to get out and cancel the purchase. … but

If the user were to leave the app (by hitting the “home” button, by hitting the “forgot password” link), then come back, then the user will be stuck on the activity indicator with the purchase screens gone… I am thinking we may be able to capture the application suspend event. But we need to do some more testing on it. If other people have dealt with this issue before, please share.

OK. I did some more testing and realized that as long as the user stays within the app, the user can still hit the back button to get out and cancel the purchase. … but

If the user were to leave the app (by hitting the “home” button, by hitting the “forgot password” link), then come back, then the user will be stuck on the activity indicator with the purchase screens gone… I am thinking we may be able to capture the application suspend event. But we need to do some more testing on it. If other people have dealt with this issue before, please share.