RECEIVE_BOOT_COMPLETED permission automatically added

[Michal]

Hi,

I've got an issue with the android.permission.RECEIVE_BOOT_COMPLETED, which is automatically added after updating the Admob's SDK to 19.6.0 from 19.4.0 on Android. The game is on Unity and we're using ironSource adapter and Gradle to install the SDK. 

We're sure that it's Admob's adapter/SDK that requests the permission, because we've checked it one by one, adding and removing each SDK.

Do you know what might be a cause of this issue and how to omit this permission?

Thanks,

[Mobile Ads SDK Forum Advisor Prod]

Hi Michal,

Thank you for bringing this RECEIVE_BOOT_COMPLETED issue up to us. I checked our Java Sample App Banner Example running SDK version 19.6.0 in the apk analyzer in Android Studio and that permission is requested. Could you state in business terms how this permission is causing you trouble?

Regards,

Aryeh Baker Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2B1nqk:ref

[Michal]

Hi Aryeh,

Thanks for a response!

From what we've found in the description it can negatively affect UX. Also, we didn't see this permission in the previous SDK versions and haven't found any information that it's being added and what's its purpose. Could you please elaborate on that?

RECEIVE_BOOT_COMPLETED

Added in API level 1

public static final String RECEIVE_BOOT_COMPLETED

Allows an application to receive the Intent.ACTION_BOOT_COMPLETED that is broadcast after the system finishes booting. If you don't request this permission, you will not receive the broadcast at that time. Though holding this permission does not have any security implications, it can have a negative impact on the user experience by increasing the amount of time it takes the system to start and allowing applications to have themselves running without the user being aware of them. As such, you must explicitly declare your use of this facility to make that visible to the user.

[Mobile Ads SDK Forum Advisor Prod]

Hi Michal,

Let me bring up your concerns with the rest of my team. We will get back to you as soon as possible.

[Michal]

Hi Aryeh,

I've just wanted to check if you have any news in regards to this issue or any ETA when can we expect the answer. We've decided to put on hold the updates of our apps, before solving it.

Thanks,
Michal

[Seddiki Aziz]

Merci

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-admob-ads-sdk/6df6adde-63da-4d04-826d-8be9108c449bn%40googlegroups.com.

[Anuar anuar]

Bounjour a tous amigos

[Michal]

Hi Ariyeh,

Any news here?

Thanks,

Michal

[Michal]

Hi Ariyeh,

Are you still investigating this issue?

Thanks,

Michal

[sailend...@gmail.com]

Is there any update on this issue? Is it a necessary permission? Or is it safe to remove this permission manually?

[Mobile Ads SDK Forum Advisor Prod]

Thanks for brining this to our attention. It turns out that the GMA SDK is not adding this but Play Services is: https://medium.com/glucosio-project/how-libraries-can-silently-add-permissions-to-your-android-app-620911d7de6c

Thanks.

ref:_00D1U1174p._5004Q2B1nqk:ref

[sailend...@gmail.com]

Is it safe to remove it manually? I have not added Play Services myself, I just use the official AdMob plugin for Unity, so is Play Services a part of AdMob Unity plugin? Please let me know.

[sailend...@gmail.com]

Is it safe to remove that permission manually from the manifest, I am getting many 1 star reviews just because of this permission, they are mentioning that they don't like this permission. And is there any update on this issue or what is the actual use of having this permission in the AdMob plugin.

[Mobile Ads SDK Forum Advisor Prod]

Using the guide from Jon's earlier post, the permission is being added by the androidx.work library, and androidx.work is a dependency of the Google Mobile Ads SDK. I'm not sure of the side effects, and since it's baked into a dependency, it's not so easy to answer. I will inquire more about the possibility of using a different dependency to side-step the issue, but in the short term would not recommend removing the permission.

Thanks,
Eric, Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2B1nqk:ref

[Igor]

So was the problem fixed? Can we remove it manually?

I'm still having this permission added to my app.

[sailend...@gmail.com]

Is there any update on this issue? It's been more than a year, the permission is still added by AdMob, and users are giving me 1 star reviews. Please respond.

[Mobile Ads SDK Forum Advisor]

Hi Sailendu,

androidx.work is still needed in our SDK. We don't know the side effects, but for workarounds please test removing the permission like:
<uses-permission tools:node="remove" android:name="android.permission.RECEIVE_BOOT_COMPLETED" />

Thanks,
Jill
Google Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2B1nqk:ref

[Mobile Ads SDK Forum Advisor]

Hi Sailendu,

Thank you for your patience. We have addressed the issue that you have brought to our attention. Upgrading your Android Google Mobile Ads SDK version to the next released version (21.3.0) should resolve your issue

Thanks,
Justin
 

ref:_00D1U1174p._5004Q2B1nqk:ref

[sailend...@gmail.com]

Hi Justin,

That's great news, thanks a lot for fixing the issue, I will be waiting for (21.3.0).