restoreTransactions generates too many calls to onPurchaseStateChanged

[pfjborg]

I have a test installation of a working app with 3 purchases and 2 cancellations of the same managed item.

However, a call to restoreTransactions results in 10 calls to onPurchaseStateChanged: I get 4 purchase notices and 6 cancellation notices.

Billing debug shows 4 PURCHASE_STATE_CHANGED messages received from Play.

As this is a restoreTransactions test I am forced to use a non-debug signed version of the app so can't trace or break to see what's going on.

Any suggestions greatly appreciated...!

[pfjborg]

More information: I inserted as line 381 of BillingController a line to log product, state, notification ID and order ID.

It seems that the messages coming back from Play include results for more than one order.

Of the four messages sent by Play 1 contains a "purchased" response with a notification id of Null but a valid order ID, and the other 3 all contain details of all 3 orders, 2 cancelled and 1 purchased in each message. Each results in a call to "onPurchaseStateChanged". Is this intended behaviour?

[ludocrazy]

i'm new to using AndroidBillingLibrary and i may be mistaken, but are you aware of what the official google documentation says about the fact that NOTIFICATIONS can come multiple times and your code must be able to hand that fact. the docs give several examples.

http://developer.android.com/guide/google/play/billing/index.html

if i am right, and you simply missed a detail from the docs, then please close this issue! thanks :-)