Termux:Task action executed asynchronously (i.e. doesn't make Tasker wait for it to finish)

[termux]

Termux:Task action executed asynchronously (i.e. doesn't make Tasker wait for it to finish)

[dugite-code]

For anyone looking for a work around Like I was using Installing the Termux API app you can issue intents back to Tasker. You will have to split your task up into chunks but it's the best I could come up with.

In a bash script

am broadcast --user 0 -a net.dinglish.tasker.totals -e totals "${calculated}"

In Tasker

Add a new profile: Event -> System Event -> Intent Received

Action: net.dinglish.tasker.totals

The variable %totals will be available in the task

[jschwinger233]

same issue, I am to make some 'meta programming' in Tasker, here's the steps:

1. call termux:task to run a script that renders a xml file
2. call import data to import rendered xml as a task
3. call perform task for imported task

the problem is step 2 starts before step 1 finish, and I haven't got a elegant way to make it.

[ks9208661]

The 19 January 2020 update (0.4) may have finally brought us some form of synchronicity.

I deinstalled version 0.3 and installed 0.4. After that I ran a test. I have a script with the following lines:

sleep 5
echo Finished

In Tasker I created a task with 2 actions:

1. Termux:Task action to run my script above, with the timeout setting to 30 seconds
2. Flash %stdout

When I ran this task, it flashed Finished after 5 seconds.

Thanks Fredrik!!!

The phone I tested this on is rooted though. When I tried this in my other, unrooted phone, for some reason I'm getting an error. It runs the Termux action but waits the full 30 seconds, and then I get a an error (I see Termux: plugin comp: com.termux.tasker/com.termux.tasker.FireReceiver and some lines regarding add wait type, but the last line simply says Error: null). The settings for both phone, with the exception of one being rooted and the other one not, are the same (e.g. Termux and Termux:Task can auto-start, run in the background, do not care about battery, etc). I can overlook this issue for now since my rooted phone is the one I use for the stuff I'm doing, and things seem to work there.

[agnostic-apollo]

@ks9208661 the wait type issue should be solved in version 0.5. Check number 9 in Issue 36 for details.

[agnostic-apollo]

Check fecba50 for disabling wait for background commands. Other issues mentioned likely don't really apply anymore. Closing.