Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Response code of BillingController.restoreTransactions() in case of errors #107

Open
dbarkar opened this issue Nov 20, 2012 · 1 comment

Comments

@dbarkar
Copy link

dbarkar commented Nov 20, 2012

I know that BillingObserver.onTransactionsRestored() is called when transactions successfully restored. Is it possible to find out if RESTORE_TRANSACTIONS request finished with errors?
When I call BillingController.restoreTransactions() I see in logcat "Request 4893727498997809316 received response RESULT_DEVELOPER_ERROR", that's ok but BillingObserver.onRequestPurchaseResponse never called :( Or may be it's called in release versions? How can I get response code using this library?

@dbarkar
Copy link
Author

dbarkar commented Dec 14, 2012

Thanks for the answer, I'lve already fixed this adding
onTransactionsRestoreFailed to the BillingObserver

2012/12/14 Michael Contento [email protected]

@mastermind- https://github.com/mastermind- that's because
onTransactionsRestored is only called if the ResponseCode == RESULT_OK.
But this can easily be fixed with this patch:

diff --git AndroidBillingLibrary/src/net/robotmedia/billing/BillingRequest.java AndroidBillingLibrary/src/net/robotmedia/billing/BillingRequest.java
index 8362559..f18f55f 100644
--- AndroidBillingLibrary/src/net/robotmedia/billing/BillingRequest.java
+++ AndroidBillingLibrary/src/net/robotmedia/billing/BillingRequest.java
@@ -217,9 +217,7 @@ public abstract class BillingRequest {
@OverRide
public void onResponseCode(ResponseCode response) {
super.onResponseCode(response);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant