CODEWITHSUNDEEP
androidandroid-manifestandroid-permissionsandroid-6.0-marshmallow
Stals
Stals

Reputation: 1603

Android 6 target sdk=23 permissions on install

I know that if you set target sdk to 23 you now need to ask the users for "dangerous" permissions at runtime like was responded here: Android 6.0 Permission Error

But some permissions are listed as "normal" and they are required when the app is installed. Is it possible to somehow mark some of the "dangerous" requirements that we have in our manifest to act as "normal" (to require them on install and not at runtime) because without some of them the app cannot actually function properly. Just rewriting everything to ask permissions at runtime is not really an option at the moment, but we will probably do that in the future.

Upvotes: 0

Views: 2901

Answers (2)

Budius
Budius

Reputation: 39846

No. There is no way to do what u want. If you don't have the time to develop it now, you should target SDK 19 (permissions were introduced on Lollipop 21)

edit:

my bad, you should target API 22, as permissions were introduced on API 23. But still, target a lower API is the best option until you have time to properly develop the permission model.

Upvotes: 3

Gabriele Mariotti
Gabriele Mariotti

Reputation: 364770

Is it possible to somehow mark some of the "dangerous" requirements that we have in our manifest to act as "normal" ?

No it is not possibile.
The only way to avoid managing the runtime permissions is to use target 22.
But pay attention.

The users can revoke permissions from any app at any time, even if the app targets a lower API level

Upvotes: 1

Related Questions