In short, using Pick Photo action returns with the images URI path but when trying to use it in send intent for example it fails. To fix that you need to get the full path using SQL Query like here:

https://www.reddit.com/r/tasker/comments/1enzuix/how_to_copy_filesmedia_from_your_android_phone_to/

The example is shown below the title: "Pick Photos/Media dialog".

Can you maybe have another variable/array inside the Pick Photos action that will hold the full path.  

Hello,

In tasker app there is no decimal

Please include decimal number in "Task"  variables "Variable add > Value"

1. I can not add decimal number like 0.5 or 0.3 or 0.003, I suggest to inlude three to four zero after points = 0.0001, hence can use it

Nowadays, there are two complications of each type for AutoWear. More and more watchface accept more than 4 complications at the same time.

Can you add more than two of each type ? 

In ordrer to change secure settings locked in the lastest Wear OS versions (Wifi for example) without developper options remain activated everytime.

Idea: Make JSONPath syntax available in tasker.

Currently JSON query syntax in tasker does not support the JSONPath standard (currently in proposed status) as described in https://www.rfc-editor.org/rfc/rfc9535.html and https://en.wikipedia.org/wiki/JSONPath

In particular arrays are awkward to deal with, especially for more complicated structures (arrays in objects in arrays... etc.)

It's possible to work around this at the expense of additional tasker actions, or by using Javascript(Let) but it would be preferable if the standard was provided for.

Some examples which don't work well are: %my_var(N)            Nth element of unnamed array. Have to use the rather ugly

Newer Android phones have "Advanced Messaging" which isn't recognized as SMS or MMS messages so Tasker is not able to capture or react to these events.  Would like to have Tasker support this new message type.  Samsung Galaxy S8 and S9 phones on ATT in US support this feature. See ATT info here: https://www.att.com/esupport/article.html#!/wireless/KM1062086

See more info here from other Tasker users: https://groups.google.com/forum/#!searchin/tasker/rcs%7Csort:date/tasker/4IRssi2DWO4/AH3a9a-CAwAJ

Support for Tasker on Android TV. 

- Download / Update via PlayStore

- Opening without Sideload Launcher

- DPI adjustments, so the top bar with burger menu isn't cut off on some devices

- Bonus: usability with tv remote

- Bonus: ability to recognize / simulate tv specific keys like input or netflix

Hello Tasker Community,

1. Synchronous "Perform Task" Option: It would be beneficial to have a synchronous version of the "Perform Task" action in JavaScript. This would be particularly useful when we need to wait for a task to complete before proceeding.

2. Plugin Compatibility in JavaScript: Exploring ways to improve plugin compatibility with JavaScript actions, such as AutoInput plugins, could open up new possibilities for automation.

3. Update JavaScript Library: Updating the JavaScript library to include all native actions would help streamline JavaScript usage within Tasker.

4. Logging JavaScript Console Output: A feature to log JavaScript console output to a file would be handy

Hi this is a request for addition of a built-in javascript function for setting display brightness (eg displayBrightness(int level, bool disable safeguard, bool ignore current level). As it is now, HTML sliders created in tasker webview element must call performTask() to change brightness level, causing laggy behavior on slider value change. Thanks! 

• Currently "perform task" from JavaScript is asynchronous only and task results are unavailable. It would be good to the option of having a synchronous version which returns results as an additional option. Sure, it's not included now for a reason. But it would be good to have the option even if it would just fail when you e.g. run a task with another JavaScript action in it.
• Currently plugins are not usable. I can see this being basically impossible to address from within JS directly, so perhaps the first point is the best solution here.
• Update JS library to include