Tasker Permission Errors

[coralwo...@gmail.com]

Device: Samsung Galaxy Note 20 Ultra 5G running Android version 12 with Samsung One UI Version: 4.1; Tasker version 5.15.14

Can some explain why I am now getting the following errors and how to resolve them. I have already given Tasker permission and still getting the error messages.

[Brenden M]

For example, I get an AutoInput error just like that when a particular profile triggers a task with an AutoInput Action that tells the UI to tap on a particular text visible on the screen. However, when I trigger the profile but the AI action cannot run because I tap the screen quickly, then the particular text is no longer visible, and that AutoInput Action error appears just like what you are experiencing. Something like that might be happening.

It isn't any sort of OS permission error, but it is an Action error. It basically means it tried to do something but couldn't. Inside the action there is a tick box "Continue After Error" and ALSO there is a "Stop Reminding" button. If you do NOT "continue after error" you must do something else. It's basically a topic called "error handling" that programmers constantly have to do, and it isn't even necessarily a sign something is not working like in my example above when due to my intentional tap, I can stop the AutoInput Tap Action from activating. (I even use a "wait" action to help do so now).

IF your profile and tasks are running properly, and such as in my case, I tapped the screen quick and THAT is why the Action Error occurred, THEN you can safe "continue task after error" or "stop reminding".

BUT, if your profile and tasks are not running properly, then these error messages can be helpful clues about which actions are having some issue doing something.

[coralwo...@gmail.com]

The suggestions you made did not work. Tasker is still giving me the same error (this is beyond frustrating) and the profile/task fails and does not execute as it used to in the past.

[RSF]

1. It may be helpful to get additional information. For your Run Shell actions, can you add the option to store output (both stdout and stderr) into variables, and display them if the action fails? Also, what happens if you tap the notification where it says "Click for more info"? Does it provide any additional information?
2. Based on the partial task descriptions shown, it looks like most of these errors may occur on some type of file manipulation (e.g. listing, deleting). Android, especially recent versions, is fussy about giving access to folders to apps. Any chance that a folder got renamed, or deleted, so it doesn't exist anymore? Any change in permissions related to folder access?
3. Try posting screenshots or descriptions of the tasks / actions that raise the errors.

[aa6vh]

I was getting those strange AutoInput errors a week ago, and could not figure out why. But they disappeared after I rebooted the phone. Maybe something in memory got corrupted?

[RSF]

Good to hear the issues resolved.

The 1st rule of tech support: reboot... As annoying as it is to hear that from a tech support representative, sometimes it actually works...