Authentication is required. You need to sign in to your Google Account. -Google Play In-App Purchase(IAP)

Issue: Google Play In-App Purchase(IAP)

While working with Google Play In-App Purchase feature, follows

After uploading Trivial Drive app in Alpha Testing, and configuring Store listings and In App products and charges, published app in Google Play Developer Console.

While testing the Trivial Driver app,


on a device with test account… Im able to Buy Gas


but when i tried to click on button for Upgrade My Car, or Get Infinite Gas, I see following error

In-App Purchase

At first I just confused about it. Later I find that there is a difference between Product Id that I created in In-App Products Developer console, and SKU_Productid constants written in code. as shown below In code

 // SKUs for our products: the premium upgrade (non-consumable) and gas (consumable)
    static final String SKU_PREMIUM = "premium";
    static final String SKU_GAS = "gas";

    // SKU for our subscription (infinite gas)
    static final String SKU_INFINITE_GAS = "infinite_gas";

In In-App Products


SO, I just changed code for SKU_ProductId constants to match with In-App products created in Developer console. And Changed application version code and name in manifest file, Generated new APK file and uploaded to Developer console Alpha Testing. After 2-3 hours waiting, its got published.. and I see everything is working fine. to summarize whole thing, you just need to use same SKU_ProductId in code, which is created in In-App Products developer console.

Hope it helps somebody…

Few other reference for In-App Billing app testing





  1. roja | | Reply

    how to check if the application is already purchased or not. pls reply as soon as possible.

  2. Alex | | Reply

    I’m implementing subscription for an app and I get the authentication required message. Is it required to publish the app? If so, can I not make it go to Play Store while I finish implementing and testing this?

Leave a Reply

Your email address will not be published. Required fields are marked *