Android In-App Purchase Authentication Required Error

Our simple blueprint game/app uses Android/iOS for achievements, leaderboards and in-app purchases. We have all of this working just fine when we deploy to iOS. However, on Android whenever we initiate an in-app purchase it errors out saying “Authentication is required. You need to sign in to your Google Account.”.

Now, this is a distribution build that was fully reviewed and published to the store. In our blueprints we are making sure to sign in before the in-app purchase node is fired off.

Our in-app purchase bp path looks like this:

I’m not sure how to address this issue.

Here is the provided log. I’m not sure why the log says Async task ‘Login’ failed in 7.7 seconds even though I see the on the screen ‘Welcome back [name]’. I’m also able to read/write achievements as well as restore in-app purchases…
[link text][3]

OH and we do have the necessary permissions… at least the billing one:

  <uses-permission android:name="android.permission.INTERNET" />
  <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
  <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
  <uses-permission android:name="android.permission.WAKE_LOCK" />
  <uses-permission android:name="android.permission.READ_PHONE_STATE" />
  <uses-permission android:name="com.android.vending.CHECK_LICENSE" />
  <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
  <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
  <uses-permission android:name="android.permission.GET_ACCOUNTS" />
  <uses-permission android:name="android.permission.VIBRATE" />
  <uses-permission android:name="com.android.vending.BILLING" />

After finding the specific error from the android log “Carrier billing config is null.”, I researched it and found that the in-app product was not “active”. Apparently AFTER you publish you need to make sure to activate the in-app product. You can test them while they are in-active.

I’ll respond when I can determine if this fixes the issue!

Bumping this thread. Did you solve this issue?

I believe so.

Sorry, I meant can you share your solution? :slight_smile:

Thanks.

Honestly I can’t remember as it was a very long time ago =(