Android M - update my app with a new resolution

In addition to the discussion here: behavior of installing and updating Android M permission , I would like to know what happens in the following case:

I added a new non-critical permission (other application permissions - for example, set an alarm, view Wi-Fi connections, etc.) in my application, and I want to publish this new version of my application as an update to my existing application. In the new version, the target SDK max is set to 23.

  • An application with the target SDK max 22 installed on the Android M device. When will this new version of the updates of my application on device M be the user explicitly granted access to the new permission?

  • An application with the target SDK max 22 installed on the Android L device. When this new version of my application is updated on the L device, does the user need to explicitly grant access to the new resolution or automatically update the word without user interaction?

+1
source share
2 answers
  • If you aim below API 23, then the old resolution model applies. The user must provide during installation, but on device M he can cancel the permission in the settings. After updating your application, the permission status does not change for that permission.

  • Only M devices support the new resolution model, so the user must provide it during installation. On device M, the user will provide a request at runtime.

+2
source

Any application with a version lower than 23 will by default include all dangerous permissions. Therefore, you do not need to request any permission if your version of sdk specified in the manifest is less than 23.

0
source

All Articles