# Unwanted Permissions in AAB After Removing All Unused Features — Blocking Google Play Approval

**URL:** <https://community.thunkable.com/t/unwanted-permissions-in-aab-after-removing-all-unused-features-blocking-google-play-approval/4088690>\
**Category:** Publishing\
**Tags:** help\
**Created:** [August 15, 2025, 6:47pm UTC](https://community.thunkable.com/t/unwanted-permissions-in-aab-after-removing-all-unused-features-blocking-google-play-approval/4088690 "2025-08-15T18:47:26Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![va.teamwork50ppi3ks](https://avatars.discourse-cdn.com/v4/letter/v/8e8cbc/32.png) [@va.teamwork50ppi3ks](https://community.thunkable.com/u/va.teamwork50ppi3ks)\
**Post date:** [August 15, 2025, 6:47pm UTC](https://community.thunkable.com/t/unwanted-permissions-in-aab-after-removing-all-unused-features-blocking-google-play-approval/4088690/1 "2025-08-15T18:47:26Z")

</div>

Hi Thunkable Team & Community,

I’m on the **Thunkable Pro (Accelerator)** plan and I’m having issues with **unwanted permissions** still appearing in my final AAB file **after I’ve removed all unused features** from my project.

* * *

**App Details:**

- **Project Name:** Fitness Focus BMI Calculator

- **Package Name:** `com.fitnessfocus.bmicalculator`

- **Thunkable Platform:** Latest Thunkable X Pro Version

- **Target Platform:** Android (Google Play Console)

- **Main Functionality:** Simple BMI calculator with 2 screens, no ads, no sound, no speech, no location, no background services.

- **Permissions Expected:** None beyond what’s necessary for BMI calculation.

* * *

**Problem:**  
Even after I’ve:

- Removed **Share** , **Sound** , **Speech** , and any other unused components from the Design tab

- Deleted all unused screens

- Checked that no corresponding blocks are present

- Rebuilt a clean AAB

…the generated AAB **still contains extra permissions** in the manifest (see attached manifest screenshot).  
These unnecessary permissions are **flagged during Google Play Console review** and cause delays or rejections.

* * *

**Impact:**  
This is blocking me from publishing on Google Play. I’ve already used up multiple AAB download attempts trying to fix it.

* * *

**Request:**

- Could you please check if my project still has hidden dependencies or default Thunkable components injecting these permissions?

- If possible, remove them from my project or confirm exactly how to fully strip unused permissions in the latest Thunkable version.

- Any step-by-step method to ensure a **minimal, policy-compliant manifest** would be greatly appreciated.

Thanks in advance! This will help not only me but others publishing lightweight apps that should have a clean permission set.