Hi João, per your reply on reddit to add a ticker here... I am hoping you would consider extending the back button navigation you introduced in Scenes v2 to the main Tasker navigation menu as well.

Currently, navigating two or three levels deep into a submenu, only to realize you are in the wrong place, requires returning all the way to the three dots menu to start over. A small back button at each menu level would resolve this and meaningfully reduce friction for frequent users.

Given that the component already exists in Scenes v2, this feels like a natural

add "wake on lan" funtionality

For example:

1. Labeling an action.
2. Commenting projects, profiles, and tasks.
3. Explain projects, profiles, and tasks.

Dear Joao,    many months ago I started using tasker. So far I have created everything I could mostly using autoinput since it was easier and a few tasker functions specifically for the profile part (time, event and state). The main reason I have started using tasker however is that i wanted to automate stuff I do on a daily basis. Along the way I have added the goal to integrate my devices via tasker and join and I'm still busy with that and so far it is going well. However there is one profile that i can't create since

When using Tasker with root access there are continuous root access toast popups.

Magisk is supposed to give root request toasts only when an app is using root but for Tasker I am getting like 25 log entries and alerts in 1 minute for Tasker. This is preventing me to browse magisk logs as they are getting filled by tasker. I am only using root in one task to run a shell command so Tasker shouldn't continuously request root access.

Attaching a screenshot of the sample, if we could have a toggle to prevent background root checks or add a

Hi I was trying the 'launch app' option and noticed it doesn't support Parallel Apps (common on phones like oneplus, oppo and family) it'd be amazing if you could add support for them :)

Hello, please make it possible to get small vertical sliders in scenes. 

Horizontal is no problem but vertical the sliders are very wide. 

Thank you very much!

Since Tasker has been green lighted for SMS/MMS, would it be permitted if Tasker could register as default SMS/MMS App?

I suggest this idea as with the SmsManager class/objects, we could control SMS/MMS much more. This would include building our own SMS/MMS apps, backing up/restoring, organising and filtering as well as blocking/spam filtering. It would also allow us to see hidden short codes from those dodgy SMS spammers.

Essentially, Tasker would just need to register it for now, rather than you make anything forward facing for it. Java could then do the rest. I for one would start

As of now only Notification listener and Accessibility service is available. Whereas there are a several others that hasn't been exposed yet.

BIND_APPWIDGET BIND_VOICE_INTERACTION BIND_QUICK_SETTINGS_TILE BIND_DEVICE_ADMIN BIND_JOB_SERVICE BIND_INPUT_METHOD BIND_CONTROLS BIND_SCREENING_SERVICE BIND_INCALL_SERVICE BIND_REMOTEVIEWS Shizuku

Hi all! I purchased Tasker 8 years ago via Google Playstore. I double checked it. I've now switched to CalyxOS which uses microG and the Aurora Store. The current stable release works fine with microG. No complains at all. If I, however, join the beta program, and install the current beta version (6.2.32-rc), Tasker complains about the end of the trial period. I'm not able to make it work. Deinstalling it, and re-install the current version (6.1.X) brings Tasker to life again. Have you changed the Playstore detection recently? Or anything else in that version related to the Playstore? Regards,

Using the Alert > Popup creates a scene named "Popup".  This creates a conflict when trying to import any other project that also has a scene named "Popup".  Since scene names must be unique, no one can import my projects from Taskernet for this reason.   

Perhaps create a scene with a random name that is unlikely to be in use elsewhere for Alert > Popup, or allow duplicate scene names across projects?

Hi, thanks for all you do. I LOVE Tasker! Regarding the "Notify" action, would it be possible to change the parameters of the action so that a variable itself can be shown in the notification panel, rather than just an icon which then has to be dragged down to see the variables's text? In my case, I'm trying to create a simple app to show the current local temperature (itself) in the notification panel. Thanks again, Alan R

I'm not seeing expected behaviour in 5.9.3 using Local Variable Passthrough and the Child Inheritance.

As an example;

So the value of %localvar is established in ParentTSK, then shared with SCENE1 when ParentTSK calls it, then shared with ChildTSK when SCENE1 calls it, and updated in SCENE1 via the Local Variable Passthrough.

In practice, the process does not run as expected:

As you can see, once the ChildTSK ends, even though it’s told to update the local variables in the parent task, the value of %localvar returns to its previous state.

This is not expected behaviour, %localvar from ChildTSK should

Having more than one Tasker license makes it more difficult to know which license belong to which device. That is why i am suggesting to have the option in https://taskernet.com/?licenses to add a name/Name tag to each license so it would be no brainer to know which one belongs to which device. 

I saw there was a post about it already but i thought to give it a try.

https://tasker.helprace.com/i1756-auto-update-feature

I have found out that technically everyone can do it themself by saving the date of the imported project using the api taskernet link and just to compare it with the current date inside the json data.

https://taskernet.com/_ah/api/datashare/v1/shares/$user/$project?a=0 

So how about doing something like this but built in within Tasker with every imported project?

I would also recommend having the option to control the check for new update time and excludes projects from the checkup that the user doesn't want to update.