I have a task that auto-dials MMI codes to turn on/off forwarding. This used to work fine, after an Android 14 update, the dial keypad pops up with the MMI code already entered, but does not actual dial the number. I have to manually click "call".

Would you please consider adding a millisec (msec) parameter to the Volume Up, Volume Down, and Volume Up/Down events in Tasker?

Currently, the "Additional Time" parameter accepts only whole numbers as seconds, which doesn't help if I want to configure the volume long press to 0.5 sec.

Title says.

Expected behaviour for disabled project.

1. The profiles status remains unchanged.
2. The profiles stop monitoring their assigned contexts, so they won't trigger the tasks they are tied with as if they are disabled.
3. The tasks and scenes are still useable by other projects.

I think It may be better to put the 3rd point under the action that toggles the project so user could have more control over their behaviour.

Some additional actions or variables may be needed to query their status, and retrieve the project list.

Change the add action button (the + dealy) such that it adds the action above the currently selected action as if "insert action" from the menu were clicked.

Add an onExit task to scenes such that when one presses the back button or the tiny little "x" the bottom-right corner of the scene said task is performed. AutoInput doesn't seem to be up to the task (no pun intended) or I haven't figured it out, yet.

Edit: I found the way using the "key" tab of the scene's properties.

Source: https://www.reddit.com/r/tasker/comments/17d0dbq/load_url_doesnt_work_for_webview_element_if_the/

I'm building a project where I use the WebView element on scenes, and I noticed a possible bug that I wasn't aware about it until now.

Basically, I'm visiting www.google.com on first scene launch, using the Load URL option of the Element Web Control action. It works as expected.

The problem comes when you have an action (ie: scene button) that call the same base URL, and use it to reload the page when the scene is just created. Just like what the Home Button of a web browser does. Here, to make it work, you need include

Make "Go to task" context menu option when highlighting a "Perform Task" action. Like "Convert to if block" in actions with conditional statements.

Preferably the first paragraph of the comment section (rather than limited characters), displayed under their name and this option should be accessible a toggle.

This way, user could leave a brief description of their tasks and profiles and read them right away.

Infuriatingly, Google restricted its own Google Assistant's functionality from lockscreens, with the assistant now frequently replying "You'll need to unlock your phone for that" ...even for things as simple as asking Google for directions/navigation!

If someone had the smarts to figure out a way to utilize Tasker (with ADB) to bypass these limitations, that would be PHENOMENAL.

Perhaps Tasker/ADB could trick the assistant to thinking the screen is still unlocked?

I would like to report a possible bug related, to the following actions, when used in the same task (or different), but when one of them is executed just after the other without any delay in between:

• Progress Dialog (1st)
• Pick Input Dialog (2nd)

It sometimes happens, and in other situations doesn't.

Hi,

I created a location profile that runs when I back to home. It starts always correctly. The linked Action for this profile is an Http Request (GET) to a specific address. If I run manually the Action in tasker It works fine, but it doesn't work automatically when profile starts.

This is my exported task (obviously in the http address I replaced my personal data like home coordinates and http key with fake chars): 

I know that Ifttt has it's own location trigger but it works very bad. So after more and more tentatives I'm trying the Tasker way.

I propose extending Tasker's "Intent" feature to not only react to URL schemes but also to allow users to edit the "android:path" component of the URL. Specifically, I would like to have the ability to trigger Tasker tasks when clicking on a link that leads to a URL like "https://www.mywebsite.com/customcommand," where the "android:path" component would be "www.mywebsite.com/customcommand."

Use Case: The primary use case for this feature enhancement is to enable Tasker to execute tasks on my Android device without actually opening the corresponding website. For example, if I click on a link that directs to "https://www.mywebsite.com/customcommand," Tasker would recognize the

Hi, I have a Direct-Purchase licence registered on an Android device dedicated to old games and in this device the tasks do not work without an internet connection. I know that the Google Play version has this limitation but does Direct-Purchase also have this limitation ?

If I export the task to APK can it work without internet connection?

Regards.

The "Required Permissions" list presented by the App Factory while creating a kid app is preventing the devs from removing "required" permissions. This means that some permissions that by Google are classified as "sensitive" will be present in the APK even if not actually needed by the app, requiring full verification by Google, which may take long time for no reason. During the app testing stage it should be up to the dev to determine which permissions ACTUALLY are required for the app to function properly, not (what sometimes seems to be the case) by generalized "guesses" by the app

An anchor (label) action that works like the "If-End if" action to easily identify what the next 3-5 actions are about within a task.

From▼(action) ▲To

This post is probably not within the scopes of what Tasker should be able to do, but I would be happy if it can happen.

I have AutoWear already and don't get me wrong, it is a great tool. However, versus the average individual who has their phone and watch synced all the time, I am not really into that. I like my device to be self-sufficient. One of the things I liked about AutoWear was it allowed me to deploy somewhat of a miniature routine to the watch in the background. For example, I used the AutoWear (default buttons)

On my Pixel 6a running Android 13, I have found that the Display -> Status Bar action incorrectly wants me to enable accessibility for it to work. I understand that on some devices accessibility is in fact needed.

This results in a few interesting quirks:

1. When creating a Status Bar action, if it is set to Expanded, Tasker warns that I need to enable the accessibility service. But the action works fine to open the notification shade even if I decline to enable accessibility.
2. If the notification shade is open, the Status Bar -> Collapsed action works as expected. But

When using a variable to create part or all of the Action Label for an action within the Notify action, the notification correctly displays the variable value in the label. However, when clicking the action label to perform an action, the performed action's %caller variable displays the variable name instead of the variable value.

Steps to Reproduce:

1. Create a task with the Alert -> Notify action.
2. In the Notify action, scroll down to the Actions section and add an action.
3. Give the action a label that includes a variable.
4. Set the action to Alert -> Flash. Set the Flash action's

Weirdly enough, tasker is not reporting the correct volume level on my head unit (Chinese aftermarket). Lots of tasks work normally, but when checking my volume level, it always returns the same value (e.g. 13 VOLM and 7 for VOLS). Anyone encountered this issue and/or has a lead on how to solve/debug this?

I bough this app specifically to control a Harmony hub. The "Tasker plugin for Harmony" says app is not available for your device in the Play Store. All threads regarding this plugin are several years old. Is there a way to use Tasker as it exists today so send remote commands to Harmony hubs?