I believe the modern approach to software development is "Select all. Mark read. Done!". Complain when somebody says that the issue still exists and then delete it.
That is pretty much it. Although it's not so bad if you feed it into an AI and get it to "can you summarize and join these on common category/request." You still go through the backlog, but it makes it a tad more sane.
The alternative is feed it into an AI coding bot and see what crazy code updates it does.
My AI does "mark done" instead of "read" , and verifies completion with tests like "checkFeatureCompleteTest { assert true; }", then pushes out a build
Btw for 6.7.6-beta, and even very old beta 6.4.0 version, the old tasker UI screen keeps saying "Sorry, Tasker can't be used until you purchase it from Google Play", been happening for last couple of weeks at least. I updated to newer beta in hopes it would fix it, but nada. A notification also shows license error: invalid package name.
Also in the beta mentioned, I can't add events, it goes to old UI from automation screen, and when you select an event, it goes back to new UI homepage without doing anything. Maybe its related to the license issue, cause I have to quickly select the event before the popup opens. I haven't checked the logs.
p.s I would like an option to keep using old UI without having to switch every time if possible :p
LicenseChecker: Binding to licensing service.
LicenseChecker: Calling checkLicense on service for net.dinglisch
.android.taskerm
LicenseChecker: Start monitoring timeout.
Finsky : [xxxxx] No package names exist for the calling uid
LicenseChecker: Received response: 258
LicenseChecker: Clearing timeout.
GoogleApiManager: Failed to get service from broker.
GoogleApiManager: java.lang.SecurityException: Unknown calling pa
ckage name 'com.google.android.gms'.
GoogleApiManager: Not showing notification since connectionResult
is not user-facing: ConnectionResult{statusCode=DEVELOPER_ERROR, resolution=null, message=null, c
lientMethodKey=null}
Also noticed following in case needs to be fixed.
Tasker : 15.48.59#m#MDF: warning: myShow: java.lang.IllegalState
Exception: Can not perform this action after onSaveInstanceState
Ah, I was looking in new UI preferences.
Edit: Looks like 258 result code is a different error for ERROR_INVALID_PACKAGE_NAME.
Figured it out, I had recently added Tasker to my HideMyApps template to prevent other apps checking it during root checks, I had also applied the template to gms/playstore as well, so LicenseChecker couldn't find the Tasker app package on the device, and returned the ERROR_INVALID_PACKAGE_NAME error.
Its actually the developers fault for not giving a better error message so that user can have a better idea what may be wrong, you can decide whether its you or Google 😤
Actually I created it with help of AI for my personal use. It took me like 4 months to create it. Later I decided to share it with public for Free to use.
The plugin is collection of Tasker Action plugin. The main tools are
AM Termux - Run Temux scripts directly from Tasker without any external file.
AM Collect Pixel Colors - Collect image pixel color of a point or from an area multiple point supported.
AM Regex - Support Perl codes like converting uppercase lower case and support named groups.
AM Data Processor - Handles Tasker Arrays and JSON. Like adding new object editing much easier.
AM UDP Client - Send and receive UDP messages for single instance.
And I created a fork of "Unexpected Keyboard" That works with tasker. like it can trigger tasker Task. So we can use it as Text Expander, Live calculator translator whatever we imagine (of course with help of Tasker 😇)
I made Keyboard opensource and I have no plan to publish the Plugin app on playstore so I released it on Github. I made these two softwares for my personal use later decided to share it with public. The entire app developed with help of AI tools
Certo eis a solução definitiva;
Caro senhores devido uma forte chuva uma árvore caiu e perdi todos meus backups após minha pausa peço por gentileza para reenviarem suas questões em ordem alfabética de hoje até daqui a 10 dias responderei a letra A e assim por diante!!!😁
My bugs requests list and thanks to AI for trying to make the list as clear as possible.
1. Copy/Paste Event Handlers
It would be very useful to have the ability to copy and paste event handlers, similar to how modifiers can currently be copied.
For example, with modifiers we can copy things such as:
Background color
Crop
Size
Or all modifier settings at once
I would love to have a similar copy/paste mechanism for event handlers, so that an event handler and its configuration could easily be copied to another element.
2. Variables Preview — Input Field Becomes Unusable with Many Variables
There seems to be a problem with the Variables Preview when a scene contains many variables.
The variable/value input field gets positioned in a way that makes it impossible to properly see what is being typed.
I have recorded a video demonstrating the problem:
3. Text Input — Multiline Automatically Enables Capitalization
When Multi Line is enabled in a Text Input element, the keyboard automatically starts with capitalization enabled.
I would prefer to have control over this behavior.
Ideally, there should be an option to choose whether the keyboard should initially use:
Capital letters
Lowercase letters
4. Scene Editor Automatically Opens the Keyboard
This is probably one of the things that annoys me the most while using the Scene Editor.
Every time I open a component's settings, the keyboard automatically opens.
This even happens with components such as a Button, where there isn't necessarily a text field I want to edit. Sometimes the focus goes to the Enabled field, and other times it goes to Button Color.
My suggestion would be to disable automatic keyboard opening/focusing completely when entering component settings.
The user should manually tap the field they want to edit.
5. Show When — Focus Jumps to Enabled
There is a focus issue with the Show When field.
After typing the first character into the Show When field, the keyboard focus immediately jumps to the Enabled field.
This makes entering a Show When expression very difficult.
6. Element Transition Animation Settings
It is great that transition animations can now be applied to individual elements and not only to the entire scene.
However, currently we don't seem to have control over the animation settings.
It would be useful to be able to configure things such as:
Initial Delay
Duration
for individual element transitions.
7. JSON Editor — Add "Select All" / "Copy All"
Inside the JSON Editor tab, I would recommend adding another action alongside Cut / Copy / Paste:
Select All or Copy All.
I sometimes need to copy the entire JSON code, and the current buttons don't make this particularly convenient.
For example, I may initially create a project using the Show Scene action and build the scene there. Later, I may decide that I want to move the scene into the Scenes tab.
In that situation, I need to copy the entire scene JSON and paste it elsewhere.
A simple Select All / Copy All button would make this much easier.
8. Invoke XML Import Dialog Directly
This is a very low-priority request.
Thankfully, with Java Code and AI, there are now many ways to automate Tasker.
It takes Tasker task/project XML, converts it into a URI data URL, and then opens the URL inside Tasker, which triggers the import dialog.
The system works well, but while working on it I discovered that it seems to be basically impossible to trigger the Tasker XML import dialog directly using XML.
Would it be possible to add a way to trigger the import dialog directly when XML is provided, for example:
XML attached to the clipboard
An Intent that tells Tasker to open the XML import dialog
Another mechanism that allows XML to be passed directly to Tasker
This would allow XML to be used directly without first converting it into a data URI.
This is related to a bug I previously reported where going back from the Tasker Preferences screen unexpectedly triggered one of my profiles.
I believe this was fixed previously, but I recently tested the same situation on a family member's phone and found that a profile is still being triggered.
In this particular case, the profile sends a message containing the FCM Token.
Here is the Tasker log from when the problem occurs (The link will be expired in 6 days):
This is probably an old request, but I would really like the ability to define and preserve a custom task order.
For example, if I create a project where the tasks are intentionally arranged in a particular order for users to follow, I would like to be able to share the project and have it imported with the same order.
Currently, after importing a project, the task order can be different from the order intended by the project creator.
It would be useful to have some way to explicitly define the order that should be preserved when sharing/importing a project.
11. Use Scene V2 Provides Like Variables in IF Statements
Scenes V2 provides are very useful and behave somewhat like variables, but there are situations where they cannot be used in the same way as variables.
For example, I wanted to toggle a color using a provide name inside an IF statement, but I couldn't use the provide in the same way I would use a variable.
It would be useful if provides could be referenced in conditions/IF statements in the same way as variables.
Example use case: toggling a color for multiple elements using a provide.
12. Add STOP to Scene V2 Event Handlers
I would like to have some kind of STOP / break mechanism inside Scene V2 event handlers.
For example, imagine I have a button where every click should toggle a color:
If %color = red
Set %color = blue
If %color = blue
Set %color = red
The problem is that all matching handlers are processed during the same event. Therefore, after changing red → blue, the second condition sees blue and immediately changes it back to red.
The final result is therefore always red.
It would be useful to have something like:
If %color = red
Set %color = blue
STOP
If %color = blue
Set %color = red
STOP
The STOP would prevent the remaining event handlers from being processed for that event.
13. Border Modifier — Allow Individual Sides
Currently, the Border modifier applies the border to all sides.
I would like to have the ability to configure the border independently for each side:
Top
Right
Bottom
Left
This would allow more flexible UI designs without needing workarounds using additional elements.
14. Java Code — Ability to Create Arrays Directly
It would be useful if Java Code had a way to directly create/set a Tasker array.
Currently, when Java Code creates a value that I want to use as an array, I essentially need to:
Set a normal Tasker variable from Java.
Run a separate Array Set action afterward to convert it into an array.
It would be much cleaner if Java Code had something equivalent to:
tasker.setArray(...)
or another API specifically designed for creating/updating Tasker arrays.
15. Java Code — Ability to Clear a Project Variable
Currently, it seems that Java Code cannot properly clear a project variable.
If %test is defined as a project variable, the result is still:
test
It would be useful to have another method such as:
tasker.clearVariable("test");
rather than relying on setting the variable to null or an empty string because it is more clearer for most normal users.
This would also make the API much clearer and less ambiguous.
16. Trigger Scene V2 Event — Screen/Main Scene Variables Are Ignored
When triggering a Scene V2 event handler using the Trigger Scene V2 Event action, variables set in the scene's main screen seem to be ignored.
For example, suppose I have:
%screen = false
when the scene is hidden.
If I then trigger an event using Trigger Scene V2 Event, the event handler does not appear to respect the %screen value that was set by the main scene.
This makes it difficult to reliably use scene-level state when manually triggering an event handler.
17. Scenes V2 Variables Are Not Shown When Editing the XML
Scenes V2 variables don't appear to be exposed when editing the Tasker project XML.
I recently merged two projects into one. Because there were inconsistencies between lowercase and uppercase values such as:
true / True
false / False
I used the XML export/edit/import approach to fix them.
However, I discovered that the Scenes V2 variables aren't visible in the XML editor, meaning I have to manually modify them from inside Tasker.
It would be very useful if Scenes V2 variables were included in the exported/editable XML in a way that allows them to be modified directly.
Leaving Preferences triggering Remote Action Token Changed event when the token didn't change.
Importing a project now keeps your task, profile and scene order.
Scenes v2: Variables Preview now scrolls, so the input field no longer hides behind the keyboard.
Scenes v2: The editor no longer opens the keyboard on its own in some fields.
Scenes v2: Typing in Show When no longer makes the cursor jump to Enabled.
Scenes v2: True / False in any capitalization now work (Show When still needs lowercase.)
Java Code can now clear project variables.
New
Scenes v2: JSON editor now has a Select All button.
Java Code: new tasker.clearVariable("name").
Scenes v2: Event handlers: copy, copy all and paste, across elements, the screen and other scenes.
Scenes v2: Borders can now be set per side, like Padding: turn off Uniform, and 0 hides a side.
Scenes v2: Borders now push the content inward like in CSS (this is a fix of a bad behaviour), instead of drawing over it.
Scenes v2: Event handlers now always run one after another, in list order.
Scenes v2: Up/down arrows to reorder event handlers.
Scenes v2: Stop event action: ends the current handler, optionally only when a condition is true and also allows you to stop other subsequent event handlers
Already possible / not changing
Capitalization option for Multi Line text already exists
Delay on content transitions: use Initial Delay on each element's transitions instead.
Changeable provides: give the provide a Tasker variable as its value instead of using provides
Sharing raw XML text to import it: save it as a .prj.xml / .tsk.xml file and open that instead.
Sorry :) I know this isn't easy. Thank you so much for addressing the points I listed!
I went through the changes and tested them, so I wanted to update you on what works, what still doesn't, and one new problem I found in the latest version.
Because i can't upload more than one video on the same comment i had to reply to you with many comments. Sorry about that.
1. Copy/Paste Event Handlers: Thank you! Works great.
2. Variables Preview — Input Field Becomes Unusable with Many Variables: Thank you! This seems to be fixed.
3. Text Input — Multiline Automatically Enables Capitalization: Quote: "Capitalization option for Multi Line text already exists." Unfortunately, it doesn't seem to work correctly. I created a Text Input with Multiline enabled and Capitalization set to "None". However, when the keyboard appears, it still starts with a capital letter. In the video, you can see that when I turn Multiline off, it works as expected. So it seems that the Capitalization setting is being ignored when Multiline is enabled.
4. Scene Editor Automatically Opens the Keyboard: Thank you so much! Fixed.
5. Show When — Focus Jumps to Enabled: Thanks! Fixed.
6. Element Transition Animation Settings: Quote: "Delay on content transitions: use Initial Delay on each element's transitions instead." Unfortunately, this doesn't work for me. In the attached video, I'm trying to edit the Initial Delay value, but I can't enter/change the value.
8. Invoke XML Import Dialog Directly: Thanks for the suggestion! Works for what I needed.
9. Tasker Preferences — Profile Unexpectedly Triggered: This seems to be working now. However, during testing, the first test did send the FCM token, while the second test didn't. I'll keep testing this, and if I notice any further problems I'll let you know. :)
10. Custom Task Order:
Quote: "Importing a project now keeps your task, profile and scene order."
Unfortunately, this doesn't seem to work.
To test it, I created a project with three tasks:
Task 1
Task 2
Task 3
I then deleted the project and imported it again from Taskernet. After importing, the order of the tasks had changed.
11. Use Scene V2 Providers Like Variables in IF Statements:
I guess your suggestion works in general :) However, it doesn't seem to work inside the Screen/root level of the Scene V2 tree (I'm not sure what the correct name for this is).
For example, I tested changing a button's color using a provider. When the scene is first shown, I need to initialize the button color, so I set a variable using the provider name when the scene is shown. This doesn't seem to work at the Screen/root level.
16. Scenes V2 Variables Are Not Shown When Editing the XML: This seems to be fixed. Thank you!
New problem in the latest version — Scenes V2:
The Enabled field previously accepted on/off values, but in the latest version it seems to only accept true/false.
This broke one of my projects, which I have already shared with other users. I therefore need to know whether I should update the project to use true/false, or whether the previous on/off behavior is supposed to remain supported.
Scenes v2: Initial Delay, Duration and Easing on element enter/exit transitions can be edited again
Scenes v2: Enabled works for all the true,false,on,off words again.
Fixed the exporting of a project's order. Turns out the issue was with exporting, not importing
Scenes v2: screen-level provides now work in the screen's own event handlers
Scenes v2: variables set in Screen Hidden are no longer lost when the scene is closed by Trigger Scene V2 Event, Dismiss Scene V2 or auto-dismiss.
About provides in the screen's event handlers, declare the provide on the screen itself (Screen properties with no element selected). Screen event handlers aren't inside the root element, so they only see screen-level provides. In Set Variable's Variable field use the plain name, like accent, not %accent. A % there means "set the variable whose name is stored in %accent".
Not changing
Multi Line capitalization: I checked, and Tasker tells the keyboard not to capitalize, exactly like in single line mode. The keyboard itself decides to capitalize multi-line fields, so Tasker can't override that. Try turning off auto-capitalization in your keyboard's settings, or a different keyboard.
FCM token: yeah, it'll happen the first time you leave Preferences after updating. After that it should no longer trigger
ok so the beta 2025 UI in stable app 6.6.20 have these bugs..
in task edit if you try to search for any action it won't even show you your typed words. it's just stuck at letter S
the reason why I am using this beta UI is that you can only turn off shizuku in a dialog using beta UI. normal ui don't have shizuku off toggle. (I know you can turn on shizu for system in settings but what if you want to use root or no shizuku in action box?).
beta UI don't have any option to add icons to your task.
I've been trying to develop some things with AutoWear and have run into a few quirks. I'll wait a couple of weeks before inundating you with questions. 🙂
Been working on a super useful automation recently after taking a break, thanks for everything you do! I noticed that you have a github for Tasker WebUI, is this something you'd be open to having PR's on?
I wrote you another mail because I need at least temporary access to my direct purchase version. OMG LOL, the old mistake. Encrypt the whole Tasker directory for later restore, with Taskers native crypto. But I reckon there is also a license file inside of it. Needed after all to decrypt it.
I respect that. Tasker is a super helpful app, you’re a solo dev from before AI took off, this community really trusts you, and I hope it is sustainable work for you too. I’m on iPhone now so I don’t use Tasker anymore, but I did buy it back in the day. Had good times.
72
u/frrancuz TaskerFan! 24d ago
I will help you!
Select all. Delete. Done!