Hi. Unfortunately, the events of the TouchTask plugin do not work again. Tasker 6.1.14 beta, Android 5.1. It was like this before too, then it worked, now it's not working again.

Hello, Joao!

Though app shortcuts are now working in google assistant in spanish, they don't seem to be fully implemented, since I'm not able to execute tasks from the assistant. Are there any plans to implement it?

Thanks in advance!

The join extension in Microsoft Edge is not working, doesn't show the devices. I think the problem is that can't sync the google account session

Yesterday I set up my LGV60 to use the google assistant button to toggle the torch.  it was working great for several hours but I believe at some point I restarted my phone and it just stopped. Restarting again has done nothing to fix the problem. Tasker just tells me torch is not available on this device.

I have Tasker 6.1.9 beta installed. The events of the TouchTask plugin stopped working for me, more specifically screen touched. Everything works on the latest stable 6.0.10.

Hello Taskers!

I'm a passionate AutoIt user for many years (an amazing automation/scripting language for Windows).

One of the most powerful functions of AutoIt is the possibility to detect screens by pixel color, because as we all know, some developers try hard to hide information from automation tools, like disguising screens with text as actually images, and that very particular feature makes AutoIt invincible in this war, because it can detect even fullscreen games with this wonderful function.

Tasker has a native Get Pixel Colors action, and AutoInput plugin has a similar action, but both require an image file.

That

V2 click action takes twice as long as v1, see reddit thread.https://www.reddit.com/r/tasker/comments/11agehx/autoinput_ui_query_too_much_info/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button

When i drag location pin, sometimes it doesnt update the location correctly or selects location near to last spot and new spot. coordinates screen doesnt update correctly when dragging. 

Tasker handling of beacons (iBeacon, Eddystone, etc. etc.) is not possible because operation of BT Near with beacons is not reliable. Active Profiles keep going inactive again several times a minute even though neither the phone nor the beacon have moved at all. Although this false reporting of "BT Beacon Gone" can be reduced somewhat by careful tuning of the monitoring parameters, it cannot be reduced to a tolerable level.

The problem acts as though for faster response _both_ Tasker and Android are trying to detect the "BT Beacon Gone" condition at the same time. This should not be happening.

Device OnePlus CPH2399 ("Nord 2T") Android 12 Tasker version 6.0.10

The state Wifi Near doesn't trigger when device's screen is off (device is locked). Only first after the device's screen goes on (device gets unlocked) does the state trigger. Other actions e.g. Beep, Perform Task, etc., can trigger when screen is off. Location Net context also can trigger when screen is off.

Tasker should make a native workaround analog to Net/Cell Wake Screen.

I recently discovered the device control tiles (also known as power menu controls) and I love them. The ability to switch my Hue lights on and off AND being able to change the brightness with a simple swipe on the tile is just so handy. But unfortunately, there is a bug. When I long press one of the tiles, the whole system ui crashes for a few seconds. This is kinda annoying because this happens quite often when I want to adjust the brightness of my lights just a tiny little bit and am too slow while swiping. Actually, I'd

I have two identical Samsung Galaxy S4, SM-GT1906, phones running Android 5.0.1 and Tasker application. Both Tasker app have the same problem: The three vertical dots at upper right corner are missing. See attachment.

One S4 is rooted and the other one is not.

Besides those S4's I have Samsung S9, OnePlus One and Redmi 8T. Three dots are okay.

So I was troubleshooting a task with someone on Reddit and I found that when I used the torch if I set the torch level with a number, like 5 it works. But if I set the torch with any variable i.e. Torch level set to %torch where %torch = 5

And it doesn't work. Does Torch not support variables? It doesn't say anything like that and it shows the option for variable select.

Hi. I downloaded taskr from the website and installed it specifically to try the trial version. I went through setup to enable a lot (maybe not all) of its functions. Then this page pops up (a few minutes after install) to say I have to buy it. What happened to the trial version? (Screenshot attached)

I have a notification with two buttons that I use as toggles. They are red when on, green when off. They toggle great during the day, but lose their colors when dark mode is activated on my phone (see attachment.)

Suggestions?

Thank you

I tried creating a battery status of my Mi Band 5 using notify but I noticed that only % appears but the value of the variable is correct. (Ex: 26)

I also tried putting the number manually, it works. But if I'm using variable, it's not working. I even tried using Variable set just to convert the match from A1 to another variable but it also doesn't work and it shows %b instead. Meaning, it's not really converting the variable into its value. Just %battery. 

    Profile: Mi Band Battery Status

     Event: Logcat Entry [ Output Variables:*

I need to launch Android Auto from Tasker on a Samsung a51-5g smartphone running Android 13 and I always get error 1 and Tasker has all the necessary permissions. I am attaching the error message that Tasker provides.

16.02.45 /Utils startActivityWrapper: activity not found 16.02.45 /Log startActivityWrapper action: android.intent.action.MAIN 16.02.45 /Log startActivityWrapper pkg: null 16.02.45 /Log startActivityWrapper cpkg: com.google.android.projection.gearhead 16.02.45 /Log startActivityWrapper ccls: com.google.android.gearhead.vanagon.home1 16.02.45 / Log startActivityWrapper flags: 805306372 02.16.45/E Launch Application: Failed to launch com.google.android.gearhead.vanagon.home1. 16.02.45/E result: stop task (error) 16.02.45/E Error: 1 16.02.45/MacroEdit action finished exeID 1 action no 0 code 20 status: Err next 0

How

I have a Galaxy S20 Ultra 5G (not rooted). Previously on Android 12. Just upgraded to Android 13, on any tasks to launch apps, I get the error "Launch App: failed to launch com.sec.android.app.xxx". It doesn't read like a permission issue. Run Log just shows "err" on the launch app task.

I've tried re-setting cache from recovery menu.  Also tried wiping data/cache for the tasker app.

Any suggestions?

I want to use the LaunchApp-function, Activity of the System Contacts-App to let the user choose a contact from Contact List. Dialog is shown properly, Contact(s) can be picked. But how do I get the results of this dialog? Are they stored in any variables?

Small white flashing box at the bottom of Tasker everytime I open it. It says "Can't connect to ADB Wifi. Check here: https://tasker.joaoapps.com/userguide/en/help/ah_adb_wifi.html"

This happens when I have zero profiles enabled, and ADB Wifi is disabled in Developer Options. I tried adding a port in the Tasker settings, but the error never goes away. Issue started after upgrading phone to Android 13, and was not having this nagging error message when running Android 12.

I've followed the directions on the link provided, but it works until Wifi Debugging is disabled (as I don't want it on), the phone is rebooted (scheduled