store.restore() does not call back on android.

Calling store.restore() never gets a callback on android.

local transactionCallback=function( event )

     print(“called”)–never called period.

end

store.init(“android”, transactionCallback)

store.restore()

I get the following printout in logcat:

D/Finsky  (31189): [14751] InAppBillingUtils.pickAccount: com.mobilexlabs.instal

iker: Account determined from installer data - [FstBw7ndXBdtPtenyT_-DzufDp4]

D/Finsky  (31189): [14751] InAppBillingUtils.pickAccount: com.mobilexlabs.instal

iker: Account determined from installer data - [FstBw7ndXBdtPtenyT_-DzufDp4]

I/qtaguid (31189): Failed write_ctrl(u 71) res=-1 errno=22

I/qtaguid (31189): Untagging socket 71 failed errno=-22

W/NetworkManagementSocketTagger(31189): untagSocket(71) failed with errno -22

D/Finsky  (31189): [1] MarketBillingService.sendResponseCode: Sending response R

ESULT_OK for request 2398093245000965829 to com.mobilexlabs.instaliker.

Any ideas? Using version 2013.1247.

Do you actually have any transactions to restore, or are you just calling store.restore() now to test it?  It’s come up a few times on the forums before: if you call store.restore() and there are no transactions to restore, then the callback will never be fired (both iOS and Android).

  • Andrew

Ah, that is probably it. No, there are no transactions to restore. Thanks!

Do you actually have any transactions to restore, or are you just calling store.restore() now to test it?  It’s come up a few times on the forums before: if you call store.restore() and there are no transactions to restore, then the callback will never be fired (both iOS and Android).

  • Andrew

Ah, that is probably it. No, there are no transactions to restore. Thanks!