android.test.purchased, not found.

[eliehanna0]

I am not able to get the test IAP product to work, however, I am able to get my Google Play Console IAP to work (up until the test payment method window is triggered at least) by uploading my app to the Alpha channel in GPC.

There is this IAP issue in the response event that I am trying to figure out, but for that I need to be able to test my game locally, the docs here suggested using "android.test.purchased" but that doesn't seem to work. I get the android.test.purchased, not found. error followed by and api not initialized message.

Here is how I am triggering a purchase.

    log(current_product);
    var _error = GPBilling_PurchaseProduct(current_product);

    switch(_error)
    {
        case gpb_error_not_initialised:
            // The API has not been initialised yet.
            log("api not initialized");
            break;
        case gpb_error_no_skus:
            // There are no SKUs in the product/subscription list.
            log("no skus");
            break;
        case gpb_error_selected_sku_list_empty:
            // There are no SKUs in the product list (although there might be
            // in the subscription list).
            log("sku empty");
            break;
        case gpb_no_error:
            // There were no errors, we should expect a response callback

            log("no purhcase errors :D ");

            break;
    }

I don't get any async input after this is triggered and I also made sure that I added the test product in the IAP async event:

switch(async_load[?"id"])
{
    // @triggered by GPBilling_ConnectToStore()
    case gpb_store_connect:

        log("store connected");

        if USE_TEST_IAP
        {
            GPBilling_AddProduct(TEST_IAP);
        }

         GPBilling_QueryProducts();

        break;
}

Am I missing a step in order to make test IAP like the android.test.purchased SKU work?

[stuckie]

Thanks for reporting this issue, but in order to investigate we will need a small project which shows this issue. Please report this issue again, but ensure you have a suitable project open at the time and you have checked the “Include Project” option on the bug form.