As reported in the subject, if I associate a task to the Android "assist app" feature, when I run it the current selected app is changed (I guess the focus is given to Tasker itself, but I am not sure hot to verify it). To avoid this, I am currently using the "Home Button Launcher" app to run the task, instead of Tasker itself: https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher
Does it help if you exit Tasker with the back button and try again?
I guess I should have explained my use case. I use Tasker to set "Location Mode -> Off" and "Power Mode -> Battery Saver" after 1 minute that I have locked the screen. I do this to save battery, but only unless I am using a navigation app. If a navigation app is focused, I keep "Location Mode -> On" and "Power Mode -> Normal", which I set when I unlock the screen.
This works fine if I lock the screen using the physical button. However I also use the Android "assist app" feature to lock the screen through Tasker, to avoid pushing the physical button. The problem is that if I use the Tasker's Assistance Request event to trigger the task which locks the screen, then the current app is unfocused (I do not know which other app is focused, maybe Tasker itslef), so the navigation apps are not detected. Instead the navigation apps are detected if I use the "Home Button Launcher" app to trigger the screen lock task.
I hope this clarifies.
