Anyone else having insane trouble with Tasker when using more than 1 profile?

43t34fg4

I am at my wit's end with Tasker + GOS profiles. No idea why it won't work. I'm sitting here opening Tasker Permissions on my PC. Everything needed is enabled/green. I've revoked and re-gave the permissions just to try it. I am using the ADB commands, just to be sure. They're working fine.

Tasker just keeps saying it is missing the write secure permission and it 100% isn't. Tasker Settings is installed properly. I have no idea where to go from here. I am on a Pixel 8 using a 2nd profile on the device. Please help. I only wanted Tasker on the one profile, but it seems unless I installed it on the owner profile, it would simply say the package didn't exist, even if it was installed on the second profile. This has been a major headache. I am getting Read.Logs error too on the 2nd profile, but not the 1st/Owner profile, even though both show enabled in Tasker Permissions.

So it's as if it is only reading things properly from the Owner profile, and not the actual 2nd profile. But the entire setup I wanted to have was Tasker just on the second profile, not the Owner one...

43t34fg4

EDIT: I think it's narrowed down to ADB/etc only working and/or reading for an owner profile and not the secondary for God only knows why. Any work arounds? But it also doesn't make sense because everything is enabled on both profiles...so, although, the PC is reading everything as enabled still for both profiles, the Tasker app itself isn't on the 2nd profile for some reason.

chinook

Yeah, so I managed to do it myself.

TL;DR: grant permissions for the package installed in the user profile.

I am using Tasker only on the first user profile (not Owner).

You probably have to install Tasker in your primary profile as well (I had to)
Enable Developer mode and USB Debugging in the Owner profile. Connect the cable to the unlocked phone, approve the connection (works only in the Owner profile anyway)

see your secondary user ID: adb shell pm list users

Users:
	UserInfo{0:SirOwner:xxxx} running
	UserInfo{10:FellowUser:xxxx} running

Grant WRITE_SECURE_SETTINGS to Tasker (you may have to do it both for the Owner and User. Maybe I was lucky)
```
adb shell pm grant --user 10 net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
```
if you have to do it for the owner, run again without --user 10
If you made a mistake, run pm revoke in the similar way
you want to verify:
adb shell pm dump-package net.dinglisch.android.taskerm | less +/WRITE_SECURE_SETTINGS +n
It should show this ("revoked for the Owner, granted for the User 10") :
```
      android.permission.WRITE_SECURE_SETTINGS: granted=false
      android.permission.WRITE_SECURE_SETTINGS: granted=true, userId=10
```
Maybe reboot? (I had to reboot :/ )
Verify it works, then disable USB debugging and the developer mode.

MORE INFO (adding so this reply can be indexed better):

Since I was using Tasker only on the additional, second user profile, and not the owner, when I run this:
adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS I was greeted with the error message:

Failure [package not found]
Error: package not found

To combat it I though I need Tasker for the primary Owner profile as well (I actually had the very similar thing with another app with the DEVICE_ADMIN permission, need to have the app in the Owner as well), and tried the advised call:

This KIND OF worked but for the owner profile only:
adb shell pm dump-package net.dinglisch.android.taskerm | grep SECURE_SET shows:

android.permission.WRITE_SECURE_SETTINGS: granted=true
android.permission.WRITE_SECURE_SETTINGS: granted=false, userId=10

-- and the Tasker in the User profile kept complaining about being unable to toggle the location.

Turns out my earlier adb call only adds the permission to the default user (Owner, UID 0).
So I poked around (adb shell pm help | less) and came up with adding --user 10.

It works.

HINT HINT:
In the below example ONLY the package in the profile 10 has the permission granted:

      android.permission.WRITE_SECURE_SETTINGS: granted=false
      android.permission.WRITE_SECURE_SETTINGS: granted=true, userId=10
      android.permission.WRITE_SECURE_SETTINGS: granted=false, userId=11

In the following example Owner and User 10 have it granted:

      android.permission.WRITE_SECURE_SETTINGS: granted=true
      android.permission.WRITE_SECURE_SETTINGS: granted=false, userId=11

See the pattern? User's permission is not shown if it matches the Owner.