Kill App Task sets system hidden_api_policy setting

[BenH]

Title basically says it all.  Tasker sets/modifies this system global setting when using Kill App either in root or non root mode.

This setting effects API  usage across the board for all apps and seems concerning Tasker sets this without request or warning.  Some security conscious apps may detect this and have issues if restricted APIs are allowed.

More info on this here:

https://developer.android.com/guide/app-compatibility/restrictions-non-sdk-interfaces#how_can_i_enable_access_to_non-sdk_interfaces

I assume Kill App isn't the only task that does this, but I narrowed it down as the culprit on my system.  My guess is it needs these deprecated calls, but this seems extreme.

Explanation as to if this is expected behavior and why?

[João Dias]

Hi. The actions that do  this  for Android 11+ are:

• ADB Wifi
• Airplane Mode
• Set Mobile Network Type

Basically they do this so Tasker can still access the needed APIs for the actions to work.

Kill App can use ADB Wifi in the background, so that explains that as well.

Hope this clarifies it.

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[BenH]

Thanks for acknowledging this.  However it is a problem.  Especially when the app is doing this without notifying the user.

Again, there are unexpected consequences for some security conscious apps that check for this setting on devices.

None of these options should require this setting if using root mode, correct?

If so, then they should not trigger this system-wide change if using root.

If they absolutely require these settings shouldn't:

a) you notify the user when enabling them that you are about to change this setting

and/or

b) enable the setting just for the purpose of running the task and then revert it automatically?

I realize that an additional command can be added to a profile to do (b) manually, however this doesn't really address the fact that Tasker is making these changes unbeknownst to the user.