-
Autoweb and Auto calendar error. help with profile.
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
-
AutoLocation Backup/Restore
Sent to support email, but trying here as well... I know from this closed post:
https://tasker.helprace.com/i1649-autolocation-can-t-backup-and-restore
That there is an update to AutoLocation to allow backup/restore on newer devices. However, that update isn't available yet on the Play Store (I am in the Autolocation beta). I cannot sideload apps on my device due to Work profile policy.
Can a fixed version be made available on the Play Store?
-
Changing depth of video element restarts all videos
Using the Element Depth action on a video element causes all videos in the scene go black and restart. This is annoying because videos take several seconds to restart.
Happens no matter what combination of element or scene settings there is.
-
Connected to specific Wifi does not work always
I have a Wifi I regularly connect to. I have a Tasker profile that reacts to this Wifi being connected to and does some tasks. I recently enabled "Private DNS" setting in Android. Unfortunately this specific Wifi does not allow encrypted DNS (a.k.a. Private DNS). This means, I can connect to the Wifi successfully, but internet access over that Wifi is not working (exclamation mark besides the wifi symbol, internet not working with disabled mobile data).
I wanted to make Tasker disable "Private DNS" when connected to that Wifi and re-enable it when disconnecting to that Wifi. Unfortunately, this does
-
Join notification steals focus when it appears.
When receiving a notification from my phone on my desktop via Tasker Join, the focus on the currently working app is stolen from the notification which means that if I am typing something, it is interrupted every time I receive a notification and I have to Alt+Tab to return to my application.
-
Need android.permission.BLUETOOTH_SCAN
On certain devices, Tasker will not be able to execute the "Net" > "Bluetooth Info"> "Scan Devices" action because it needs android.permission.BLUETOOTH_SCAN permission.
I have granted every single permission to Tasker. This effects Galaxy S20 FE with Android 13, but not Pixel 8 Pro with Android 14.
I may be able to grant with ADB, but Tasker is not properly requesting this permission or something else is wrong, as I am able to run Bluetooth scan from my own app with proper permissions on the same device. Maybe it also needs BLUETOOTH_ADMIN?
Here are the permissions my own app uses:
-
Load URL doesn't work for WebView element if the scene is not hidden/unhidden first
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
-
Dialog actions crashes Tasker in some circumstances
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.
-
Profile starts but action does not trigger
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.
-
Tasker tasks don't work without internet connection [ Direct-Purchase Version ]
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.
-
Required Permissions in App Factory
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
-
Tasker on WearOS please?
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)
-
Display -> Status Bar Incorrectly Warns that Accessibility is Needed
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:
- 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.
- If the notification shade is open, the Status Bar -> Collapsed action works as expected. But
-
Alert -> Notify: Variable Values in Action Label Not Passed To %caller for Action
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:
- Create a task with the Alert -> Notify action.
- In the Notify action, scroll down to the Actions section and add an action.
- Give the action a label that includes a variable.
- Set the action to Alert -> Flash. Set the Flash action's
-
The vibration doesn't work.
Hi. Vibrate, Vibrate Pattern actions don't work. There is no error, but there is no vibration. Android 11 Lineage Tasker beta 6.2.12-rc. All permissions from settings are obtained, as well as write_secure_settings
-
Geomarker spot colour disabled with variable spot size
When using "Element Add Geomarker" there is a field called "Spot Colour" which allows you to set the colour of the spot surrounding the marker.
If the spot radius is set to 0, this parameter disappears, which makes sense. But if you set spot radius to a variable (e.g. %marker(3)) the spot colour parameter also disappears. This means you can only use spot colour if the radius is a constant.
I imagine this isnt intended
Android: 13 (TQ3A.230705.001)
-
Tasker disable Accesibitily Service of other apps
When Tasker enable Accesibility Service for itself, it disable Accesibility Service for other applications.
Uso la pulsación prolongada del botón de volumen-arriba para lanzar una tarea de Tasker. Para ello necesita tener habilitado el Servicio de Accesibilidad. Este servicio se desactivaba cada dos o tres días y tenía que volver a concederlo.
También uso constantemente el programa Quick Cursor, que también necesita el Servicio de Accesibilidad, pero nunca lo perdía.
Cuando se añadió la opción de que el propio Tasker vigilara si había perdido el Servicio de Accesibilidad y lo volviera a conceder, me alegré y lo active tanto para
-
Scene resolution NOT updating when exported to Factory KIDS APP
I make a scene and it is 910w by 525h. I export it as an app. I then later decide I want my scene to be WIDER, so I change the width from 910 to 925. Looks normal in Tasker. When I export it as an App however, the resolution is still 910w instead of the new 925 and all my buttons are pushed horizontally into the others if they were on the edge past 910 pixels.
-
mobile network state 'active' is not set when connected using ipv6
Tasker mobile network state 'Active' does not apply when a connection is established using ipv6 only. When connected using ipv4 the 'active' state is properly set.
-
AutoTools Bluetooth Permission
Unable to determine how to add the required bluetooth connectivity permission on a OnePlus CPH2459 Nord 20 5G. When running a bluetooth related AutoTools action in Tasker, a notification will inform a requested permission is required. But selecting the notification does no action. Also attempting to add the permission via the App details page does not seem to be an available option to enable.
Android Build - CPH2459_11_C.13