question

LeonTx avatar image
LeonTx asked

onGetUserIDResponse not getting called via initiateGetUserIdRequest

We've been able to replicate on one device, an issue some of our users have reported where a previous purchase isn't getting restored. I've tracked it down to an an issue where onGetUserIDResponse isn't getting called. Instead of seeing this in the log: D/SandboxRequestHandler( 4054): In App Purchasing SDK - Sandbox Mode: sendGetUserIdRequest D/SandboxResponseHandler( 4054): In App Purchasing SDK - Sandbox Mode: handleResponse I'm getting this: D/SandboxRequestHandler(12074): In App Purchasing SDK - Sandbox Mode: sendGetUserIdRequest V/ContextImpl(12074): Implicit intents with startService are not safe: Intent { act=com.amazon.testclient.iap.appUserId flg=0x10000000 (has extras) } android.content.ContextWrapper.startService:529 com.amazon.inapp.purchasing.SandboxRequestHandler.sendGetUserIdRequest:-1 com.amazon.inapp.purchasing.GetUserIdRequest$1.run:-1 W/ActivityManager( 510): Unable to start service Intent { act=com.amazon.testclient.iap.appUserId flg=0x10000000 (has extras) } U=0: not found Since, I don't know that I'm starting the intent directly, not sure how to address it. Please advise.
iap
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

DougM@Amazon avatar image
DougM@Amazon answered
Hello LeonTx, This intent is directly fired when the In-App Purchasing SDK determines that it is in Sandbox mode, meaning that it has not been published by Amazon as either a live app nor as a Live App Test. My suggestion would be to submit a version of your app to our Live App Testing service if you are attempting to triage an In-App Purchasing issue for your customers.
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.