在运行时推送通知 (GCM) 权限? [英] Push notifications (GCM) permission at runtime?

问题描述

我读到有必要在运行时向用户询问 API 23 及更高版本的一些权限.例如:android.permission.ACCESS_FINE_LOCATION.如果 API 为 23 或更高版本，是否有必要(甚至可能)请求运行时权限以在运行时使用 GCM/推送通知?

I have read that it is necessary to ask the user for some permissions at runtime for API 23 and up. For example: android.permission.ACCESS_FINE_LOCATION. Is it necessary (or even possible) to ask for a runtime permission for using GCM/push notifications at runtime if API is 23 or higher?

我尝试在运行时使用 requestPermissions 方法，但是当我将它与任何 GCM/推送通知相关的权限一起使用时，它似乎不起作用(没有任何反应).

I have tried using the requestPermissions method at runtime, but it doesn't seem to work (nothing happens) when I use it with any GCM/push notification related permissions.

为此，我在我的清单中有以下权限:

I have the following permissions in my Manifest for this purpose:

<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE"/>
<permission
    android:name="${applicationId}.permission.C2D_MESSAGE"
    android:protectionLevel="signature"/>

用户知道的唯一权限是从 Play 商店下载应用程序时的 ACCESS_FINE_LOCATION.用户是否应该能够选择是否允许推送通知?

The only permission that the user knows of, is the ACCESS_FINE_LOCATION when downloading the app from Play Store. Shouldn't the user be able to choose whether or not they would allow push notifications?

推荐答案

其实推送通知权限在Normal Category Permission，就像INTERNET权限不在Dangerous类别权限.

Actually the Push Notification permission lie in Normal Category Permission like INTERNET permission not in Dangerous Category Permission.

您不必请求推送通知权限.

虽然联系人/位置是危险权限，因为您正在访问用户数据.所以总是需要要求用户允许它.

While Contacts/Locations are the Dangerous permissions because you are accessing user data.so always needed to ask to user to allow it.

希望你明白.https://developer.android.com/guide/topics/security/permissions.html

这篇关于在运行时推送通知 (GCM) 权限?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！