All of a sudden all of my tasks that contain Bluetooth control stopped working.  I'm on a Samsung Galaxy S22 running OneUI 5.1 which is Android 13.  My Tasker is the latest released version.

Audio Adjustment command fails to perform successfully when performed from widget, but does not report an issue. Successive steps are performed as if command succeeded. Task is performed accurately when performed from Tasker application directly, so failure is limited to only when activated via a widget.

Performed report issue to developer option via Android app.

Phone - OnePlus CPH2459

I have some tasks written to allow me to do some things "hands free" while I'm driving. They have worked well in the past, but today I noticed that they work only if Android Auto is not running. So if I say, "Run <task name> with Tasker" while AA is not running, Google Assistant will execute it with no problem. But if AA is running, Google responds with "Sorry, I don't understand".

The "Sorry" message is something I understand is expected without AA if the phone screen is off (and that still happens, of course), but I've never before gotten

Every time I leave or enter the house, the profile is activated but it shows me a message on the screen requesting permissions for "tasker settings" to enable and disable wifi. This application has always had all the permissions. So I don't know what else to do except disable the profile and do it manually.

I have just installed app factory and tasker from the play store and trying to export an app. See attached error 

these errors are appearing when I try to use the ElevenLabs GPT voice chat module. Instead of returning the voice output it will open another google assistant voice prompt dialog and display the GPT response under the microphone button where the recognized speech normally would be displayed

As above

Tasker Version: 6.0.10 App Check Method: Accessibility

OS: LineageOS 20 (Android 13) OS Code: 33 OS Target: 30

When using the Assistance Request event profile, it will consistently fail/crash with android.os.BadParcelableException in certain areas of apps. It seems to happen most often while I'm viewing an area of the app that is used for chatting.

Note 1: I can disable all event profiles that utilize assistance request, and the crash will still occur. Therefore it would seem it has nothing to do with the profiles I've created.

Note 2: I used the same event profiles in LineageOS 19 (Android 12L) 

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.