Google Play Store publishing error following Branch.io implementation

[ricolnz]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

Google Play Store publishing error following Branch.io implementation

When publishing to the Google Play Store, I received the following error:

Setting release for Google Play track internal failed.
This release includes the com.google.android.gms.permission.AD_ID permission, but your declaration on Play Console says your app doesn't use advertising ID. You must update your advertising ID declaration.

However, after downloading the code and checking it, I found no mention of this permission.
Same thing in FireBase, no Google Analytics configured; nothing has changed since my previous post.

Expected Behavior

How can I remove this permission request without adding an advertising ID ?
I find no trace of this permission request in the entire downloaded project. I don't use Google Analytics or any other similar product.

Steps to Reproduce

Simply try publishing the app on the Google Play Store

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

IT4oheflxItNtbxe+KXhYO9VhSQ4OWYkU4EZmMpBZywgfZzzBLN/fPfQP1tBUuG+dH9Yekycp14K+N7pifDEGPoVOQibUYg6wbVicQ3MRTuXbKmTF7qOXkdTN/FXG3LF58OFsSNBKu5aS0IF6maqOfK8cDHAK7rjIno8Sq/LZO4=

Visual documentation

Environment

- FlutterFlow version: v6.0.51 + released July 18,2025
- Platform: Android
- Browser name and version: Chrome Version 138.0.7204.158 (Build officiel) (64 bits)
- Operating system and version affected: Windows 11
- FlutterFlow Windows Desktop

Additional Information

I'm trying to publish the new version of my app following the implementation of the Branch.io library installed from the MarketPlace.

[rzambroni]

Hey @ricolnz, thanks for the report!
I believe the issue is related to the branch.io dependency — it likely causes the AD_ID permission to be added automatically during the build process. Since this is handled by the underlying SDKs, you won’t see the permission explicitly listed in your AndroidManifest.xml or build.gradle files.

Branch may rely on the Google Advertising ID to:

• Track installs and user re-engagements
• Attribute deep links and referrals
• Build analytics around user behavior

Because of that, the permission is injected at compile time to support those features.

The safest path forward is to declare “Yes, my app uses the Advertising ID” in the Play Console, even if you’re not actively using ads. This aligns with what’s actually included in your app bundle and avoids blocking the release.

As an alternative, you could try explicitly removing the permission by adding the following to your manifest:

<uses-permission android:name="com.google.android.gms.permission.AD_ID" tools:node="remove" />CopiarEditar

However, I can’t guarantee that removing it won’t affect Branch’s functionality (e.g., attribution or deep linking). So unless you have a strong reason to remove it, I’d recommend updating the Play Console declaration instead.