-
Task without a name when using "Convert Into Task"
When converting actions into Task it's possible to save the Task without a name.
Tasker 6.1.3-beta
-
moving media bug
Versions after 5.14.8 have an error, the action of moving a photo or screenshot from folder to folder tightly hangs the media scanner process, only a reboot helps (I tried on 3 Xiaomi mi 11 ultra, Redmi note 10 pro, Redmi note 9 pro devices).
As a result, the moved files in the gallery of any applications are missing until the reboot (telegram, regular gallery or any of the market).
Example:
A1: Wait [MS: 700]
A2: List [Directory: DCIM/Screenshots/ Sort Select: Alphabetic Variable Array: %SCREENSHOTS ]
A3: Move [From: %SCREENSHOTS(1) To: Pictures/Screenshots ]
A4: Vibrate [Time: 200 ]
A5: Scan
-
App factory icon problem
I'm unable to create (export) ANY new project as App because every time I try I get the following set of messages:
- prepare directory
- unpack factory assets
- decompress factory assets
- shrink unneeded files
- convert drawables to builtin
error: loading android.resource://com.google.android.apps.fitness/drawable/2131820556
error: failed
The above is an example where I've tried to use an existing App icon (Fit in this case). But no matter what I try, Holo, Material, Misc, Crystal HD Project, I Like Buttons HD, the same type of error occurs with different resource ids. I've uninstalled and reinstalled Tasker with no change. BUT if I change the app
-
AutoLocation should not require Storage permission
AutoLocation plugin requires Storage permission during first start. After removing that permission manually, everything works fine. Only error message toast "Permission denied" is shown during AutoLocation app startup.
Thanks.
-
IPv6 DNS cache bug
It looks like there is problem in HTP request action in combination with IPv6. It can be tested with URL https://fallback-v6.ipv6-test.com/json/proto.php which works over IPv4, but not IPv6 and contains both A and AAAA DNS records. Test task attached. There are two bugs.
Use cases:
Connected to network which doesn't support IPv6:
- Tasker gets A record
- HTTP request works - CORRECT
Connected to network which supports IPv6:
- Tasker gets AAAA record
- HTTP request fails - BUG
- there should be fallback from (not working) IPv6 to IPv4. That URL in browser loads fine (after small IPv6->IPv4 fallback timeout)
Connected to network
-
SystemUI not in list of apps to kill
I'm not sure if more system apps are affected, but at least SystemUI does not appear in the list of apps in the "kill app" action. I also can't input a package name to work around the bug.
-
Tasker crashes when creating scene
Open Tasker, click on scenes and then the orange + add button. I get the popup to give it a name. Type in any name, hit the checkmark. About half a second to a second later tasker just crashes and I am back on the home screen.
Did the report issue in tasker, included screen recording.
-
"Trial over" with degoogled phone, but I already bought it
I've been using Tasker on this device for a couple years. I purchased it many years ago and installed it via Aurora Store. Now, this device is EOL and I'm trying to migrate my Tasker profiles to a new phone. However, suddenly tasker won't run because my "trial" has expired. This is aggravating because I just want to export my profiles.
In this thread Joao said:
Tasker's Google Play version works by quering the Google Play store if it's licensed. If Google Play is not present then that will happen. You can always switch to the direct-purchase version that you
-
Cannot Accept Terms
Upon installation it is required to accept app tetms, however the terms are empty, only the following error message is being displayed:
Couldn't get terms. Please contact developer.
I am using Google pixel 4a, Android 13
-
Scene Element border distorted after resizing
After resizing an Scene Element, the element's border is distorted. Original size: https://ibb.co/JmKPhbs Resized: https://ibb.co/wzYdmFx Expected: https://ibb.co/vq755df It would be better if the border didn't change its size. There is an Element Border action for that.
-
Action Error java.lang.InterruptedException (Error Code: 1)
Task "Display Turn Off", when is launced from Quick Panel or shortcut, shows Tasker Action Error java.lang.InterruptedException (Error Code: 1) and display turned off. When it's launched from Tasker, it's OK.
-
Auto input does not disable when tasker profile disabled.
I have Tasker using a profile to intercept keys. I have the AutoInput mode Enable Just When Needed set on. When the profile is first enabled (by a task) a notification that AutoInput is running is shown. But when a task disables the profile, the notifiacation is not cancelled.
-
3 dots menu missing to adv settings
box: android 11, UT8 UGOOS
reported ALSO TO THE DEV IN CHINA VIA THEIR WEBSITE
NO COMMITTMENT TO FIX 2 MONTHS NO OTG UPDATE
request: alternative way to the 3dots to get menu like
a button at top of profiles?
tasker also seems to stop on this device.. check battery and screen overlay are correct
trying now dev options as this box comes with magicsk inbuilt superuser I turned on stay always awake to see if fixes that
-
Tasker Ticker don't show the next lines
I have the task "Ticker" installed, but I can see only the first line of a message in WhatsApp or signal. The line fades out and I can't see the next. Is there a setting I can change to see line 2, after line 1 fades out and so on?
-
android 12 wifi control not working with tasker settings 1.3 or 1.4
I used to use tasker together with tasker settings 1.3 to control Wi-Fi on my Xiaomi Redmi Note 10 with android 11.
This worked until last weekend, when my phone got an update to android 12 by xiaomi.
I then updated to tasker settings 1.4 from github, which seems to be the latest revision but still Wi-Fi control doesn't work anymore.
Is there something I am missing here?
-
"Error - accessibility not running"
I use Tasker with the AutoInput and AutoApps plugins across several devices to run tasks. Lately, I've been having actions randomly fail with the error "Accessibility service not running" despite it running quite happily for months prior. Using an AutoInput Action to click certain coordinates, doesn't not present an error, but the click does not happen. The permissions are set as they always have been and I have done nothing to change them. It is as if the service just forgets it has been set up. The only way I have found to fix this has been to clear the
-
Set wallpaper not working on Google pixel 4 xl
The set wallpaper task used to work fine until an android update some time back.
For a few weeks now this hasn't been working. Instead of setting the wallpaper to the selected image, it sets it to an image I don't recognize (the one in the attachment).
I am also attaching a screenshot of the task
-
new v6 Airplane Mode toggle not working, Android 7
This would be great for me (thanks!), but unfortunately it doesn't work on my phone: Android 7, Moto E4 Plus. I have Tasker set as Assistant and the android.permission.WRITE_SECURE_SETTINGS is enabled (I checked this using the Tasker app). When I run Airplane Mode toggle I get "Error 1, no way to toggle airplane mode, check notifications"
Malcolm
-
Autoremote error in Microsoft Edge
Hi, I'm unable to get my personal key on the autoremote extension. I installed it on Microsoft Edge (through the chrome web store), that worked well. But when I open the autoremote extension options it keeps showing 'Error getting personal key. Refresh this page to try again. Please contact the developer if the problem persists'. Thanks in advance!
-
App Factory (kid apps) crash/killed on Android 12
On Android 11, works fine. On Android 12, works fine until a day or so later, when the notification is gone and the profile won't trigger.
Using tasker and app factory 5.12.0, target Android version 26, basic permission set like LOCATION, NETWORK, WAKE LOCK, EXTERNAL STORAGE, etc. When installed it asks for location and storage permissions, and Display over Other Apps, which I grant. I also disabled battery optimization.
The Profile conditions only check for Display On, GPS On, and WiFi connected.
I know Android 12 has issues with killing phantom processes described here, but I've tried the fix using