ANR crash when trying to purchase something without having market configured about androidbillinglibrary HOT 10 OPEN

Good catch. We didn't try this scenario.

Did checkBillingAvailable provide you a positive result?

from androidbillinglibrary.

Sorry I didn't check that at the time. I'm currently crazy for a deadline on tuesday, but i'll give that a try afterwards.

Good job on the library btw, makes things a lot easier. Is there a way to -custom- inject subscriptions? eg by entering a code I'd activate a subscription on the device locally instead of via the market.

from androidbillinglibrary.

I can confirm this same issue.

BillingController.checkBillingSupported() returns UNKNOWN in cases where the market isn't yet setup. It also return's unknown if there is a pending Term's of Service agreement in the market on devices using 2.2, not sure about 2.1 or lower or 2.3. 3.x doesn't seem to have this issue, but I can only test it on one device the Motorola Xoom.

from androidbillinglibrary.

checkBillingSupported always returns UNKNOWN the first time it's executed. The actual status is sent to the observers of BillingController.

from androidbillinglibrary.

In that case the observers are passing back supported. All I could thing of doing was creating an optional call back function in the case that the app couldn't bind to the market, so the developer could throw up a warning or do something in the event that a bind didn't occur.

from androidbillinglibrary.

That's more or less what we planned to do. Not sure if we should at it to the observer interface, though. We'd like to keep it as simple as possible and this particular scenario is not very frequent.

from androidbillinglibrary.

No it shouldn't be but I've already experienced the TOS (terms of service) version of this from 3 out of my 6 testers. They don't use their devices frequently. In the case of the TOS error, the application also doesn't always crash and I've observed users continuously hit buy buttons with no response from the Billing System other than a silent "Could not bind to MarketBillingService" in the logs.

It's also worth noting that even if the users go and accept the TOS, and return to the app there is still a binding issue for a few minutes... might be an Android issue more than a BillingLibrary issue, but if it can be worked around it would make users less confused.

from androidbillinglibrary.

A)

@ophidian and @drewjw81 is this still present?

is it still reproduceable to wipe a device, NOT touch the market app (and thus not setup anything there), copy your own app onto the device and then reproduce above crash?

B)
does this crash report make sense? i mean, we are talking about google market in app purchases, that means someone needs to get your app AND needs to use google market. that means for me you will in 99,9% of all situations delive the (free) app to the user via google market. THEN he will use the billing features and thus the market will be configured properly.

if i understand the report above correctly (havent tested it myself), then the following happens:
-phone wiped, no market properly setup / TOS accetpted / etc.
-manually copied your (release build, sigend, non debuggable) APK onto the device
-app is started, library properly returns SUPPORTED and then simply does nothing when touching a "BUY THIS" button?
-because if it throws the NPE on the service, this means the intent is not started, which means that in a typicall code logic triggered by a button press nothing else is disturbed by the NPE.

correct?

from androidbillinglibrary.

I also have that issue, not produceable on my side but it is logged on developer console as it comes to some user for one of my game in android market.

from androidbillinglibrary.

Can u help me on that..?

from androidbillinglibrary.