Add Ad ID Permission Declaration in PWABuilder Packager Tool

[ekkaiasmith]

Tell us about your feature idea

It would be beneficial to add a feature in the PWABuilder packager tool that allows developers to declare the Ad ID permission (com.google.android.gms.permission.AD_ID) directly. This feature should automatically insert the following permission into the AndroidManifest.xml when building the Android package for a PWA:

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

Do you have an implementation or a solution in mind?

Add an option in the PWABuilder interface where developers can specify whether their app requires Ad ID permission. If enabled, the packager will automatically add the following permission to the generated AndroidManifest.xml file:

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

Have you considered any alternatives?

Currently I don't see any other alternatives than to decompile the .aab and editing the manifest myself.

Tasks

Preview Give feedback

No tasks being tracked yet.

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[ziadwagdy]

I faced the same issue and resolved it by enabling the "Include Source Code" option while packaging for Android.

After that, I was able to edit the AndroidManifest.xml file directly and add the required permissions.

Then, using Android Studio, I navigated to Build -> Generate Signed App Bundle or APK and generated my signed .aab file, which worked perfectly.

This method offers an alternative solution.

[victorsferreira]

shouldn't we just mark this option as "NO" when submitting the app?

[jgw96]

I faced the same issue and resolved it by enabling the "Include Source Code" option while packaging for Android.

After that, I was able to edit the AndroidManifest.xml file directly and add the required permissions.

Then, using Android Studio, I navigated to Build -> Generate Signed App Bundle or APK and generated my signed .aab file, which worked perfectly.

This method offers an alternative solution.

Hello all!

So, for this, which is something that is not and should not be in all apps, we prefer users to instead add any new permission declarations yourself using Android Studio. This is the reason we have the "Include Source" option. We could support this permission in our UI, but then we go down a slippery slope of having to support every Permission in our UI.