Skip to main content
Question

AndroidManifest.xml com.android.vending.BILLING always required?

  • January 17, 2025
  • 4 replies
  • 145 views

Forum|alt.badge.img

Is the following still required in my AndroidManifest.xml?

<uses-permission android:name="com.android.vending.BILLING"/>

the Flutter installation guide doesn’t mention it but I’m following a video which explicitly recommends it.

It’s mentioned a couple of times in relation to react native.

This post has been closed for comments

4 replies

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 277 replies
  • January 17, 2025

Hi ​@Michael Dausmann! This is not required for Flutter.


Forum|alt.badge.img

Hi ​@jeffrey_bunn thanks for responding.  I found that I needed to add it and push a version to the store (not production) with it enabled in order to start setting up products...maybe I’m dreaming and I muddled it up.  This is my first app with in-app billing, if that clarifies things.


  • New Member
  • 1 reply
  • January 23, 2025
Michael Dausmann wrote:

I found that I needed to add it and push a version to the store (not production) with it enabled in order to start setting up products…

I was also fresh to Google Play and I experienced the same.

Before uploading a bundle with:

<uses-permission android:name="com.android.vending.BILLING"/>

in AndroidManifest.xml, I couldn’t create any subscriptions.

There was a button that said “Upload a new APK” which redirected me to the “Closed testing” tab and I didn’t know what I had to do.

It would be extra cool to include that in the docs here https://www.revenuecat.com/docs/test-and-launch/sandbox/google-play-store


jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 277 replies
  • January 30, 2025

@obasilakis ​@Michael Dausmann Thanks so much for sharing! I’m communicating with my team, and it looks like you might need the BILLING permission only initially to unlock creating products in Google Play (as you both reported). I’ll try to confirm and add a note to our documentation. Thanks again!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings