While App Factory is no longer support for new actions since 6.6, the thread leak in Java code that was fixed at 6.7.3, is still present in any app generated by App Factory.

Regardless whether they are generated by 6.7.3 or above.

I hope that this can be fixed as it could cause the device to lag once it hits high numbers.

Link where the leak was fixed. https://www.reddit.com/r/tasker/comments/1sqs68t/dev_tasker_673beta_scenes_v2_update_2_and_some/

Link where the leak was reported. https://www.reddit.com/r/tasker/comments/1s3fz5o/comment/oghjs8a/

Tasker automatically creates variables for the extras in an Intent Received trigger, but those variable names can (rarely) conflict with existing Tasker variables:

https://groups.google.com/g/tasker/c/k03Lw8tGSHA

Giving an option to add a prefix to the extras' variable names, like in the Get Calendar Events action, would fix this issue without impacting the functionality of existing tasks, e.g. the conflicting %priority extra could be changed to %ntfy_priority.

I have several old profiles set up with Cell Near as a trigger, and have never had an issue with them until recently, when my evening profiles failed to trigger (the morning ones involving Cell Near triggered perfectly, and that was the last day any Cell Near profiles worked).

While troubleshooting, I realized that my carrier finally activated 5G Stand Alone (maybe part of the 2G/3G shutdown?). As a result, Tasker is unable to use Cell Near to scan these new cell IDs, the page remains blank even after scanning for 10+ minutes.

Does anyone know how to force Cell