I would like to report something related to the Text Input element from scenes.

When you just create it (and show it) a bottom line that tells the user that this is a text input type field gets appeared everytime the scene is shown (created), but when you visit/tap the Background tab it gets dissapeared permanently. You need to delete and create the element again, and avoid entering to this tab again.

I can create something like a little frame using the Rectangle element, and also it would end cleaner, maybe... But I just wanted to report it because I

I tried to import a project to an old phone and it failed. After a bit of investigation I found that the List Dialog and Text Dialog are not shown in the Input action group. That is, unlike other settings, they don't show red with a message telling you what version of android is needed. Also, I don't think they should be missing, as the dialog used by Text Dialog is available on Android 6.

This is with the latest version of Tasker.

Hi Joao, I have a question regarding to the scenes. When an Overlay scene is created when the screen is off, the screen remains off. But when a Dialog or Activtity scene is created, the screen automatically becomes on. Can this behaviour be changed on future releases, so the screen doesn't turn on? Or is it a Tasker/Android limitation that cannot be "fixed"? We already have the Turn On action to manually turn it on. Thank you ;) - - - - - - - - - - - - - - - Source (Reddit): Go!

Hello , My device model is mi 6. 

When I use ADB wifi on Tasker, the prompt is sh adb Not Found，As shown in the figure below.

My device system info : I can provide you with the test, my email is: , please use Base64 decoding How to solve this problem?  TKS.

A few months ago i was having trouble with a profile that sends an SMS prompting an unknown (not in address book) contact to identify itself. The profile sometimes stopped sending the SMS so i added a second text file that logs every caller id regardless. Since then everything seemed to work fine until a few days ago when the app, once again, did not send the SMS as instructed. It turns out that tasker detects a zero as a caller id when in fact it is plainly visible in the call logs. Is this a known bug?

------------------------------------------

Profile:

I'm trying to Edit the AP Config of a web service that I've added to Autoweb so that I can hide the sensitive details and then share it. But it comes up with a "failure from system" error when I try to edit the config. If I copy and paste the web service, I get the same error with the pasted web service.

I've not encountered this before.  For all the other APIs in my AutoWeb app, I can Edit configs without issue. I've tried restarting my phone. There's nothing about the error in the AutoWeb log (detailed logs selected). The

Adb wifi after doing adb tcpip 5555, If i run task "test", getting error 1 and Action Timed out error. device- oneplus

tasker ver: latest beta6

%array(#?~Ra(bc)?d) fails. Work round is to put regex into a variable and use (#?~R%regex)

Although I've done ALLL permissions. https://photos.app.goo.gl/npD2mBtqkGGUivy97

If I have any time contexts (eg. instant context that runs at 09:00, or a time context that repeats every hour), the tasker monitor wakes up every single minute.  Nothing appears in the run log for this obviously, however you can see it in Battery historian and in the tasker debug log.  Disabling all time contexts stops this from happening.  Enabling a single simple time context causes the activity.  The problem occurs no matter if "Use Reliable Alarms" is enabled or not.

Debug log:

15-05-2020 ReceiverStaticInternal: 10.49.00#m#ReceiverStaticInternal: r: net.dinglisch.android.tasker.ALARUM 15-05-2020 WakeLockManager: 10.49.00#b#WakeLockManager: acquired partial lock for M flags: 1 autorelease:

And when I choose "long" it get even shorter.

Tenho a versão paga (última do play store). Não estou conseguindo criar regras no estado ou evento, porque?

I have a problem with Tasker.I bought it about 8 months ago,with a Google Play gift card,and after I bought some plugins.After 4 month tasker said that the demo try is ended and you have to buy tasker or something like that.I searched a way to contact you,but I didn't find it and I forgot this think,but now that I have to use it for a project, I must have back Tasker or have back my money!!

Hi, I have an issue with the Outgoing Call state profile in Tasker as described below:

Issue Context:

I have created the following simple profile:

Profile Trigger >  Outgoing Call (found in State section)

Actions > Notify (text is "hey you are making a call to this person named %CNAME with number %CNUM)

Problem:

When I make an outgoing call, this profile worked perfectly. but thereafter no matter how many outgoing calls I make, it always displays the wrong caller data (triggers the action but %CNAME and %CNUM are still pointing to the very first caller data, meaning they're not

I have already tried to search on internet, and I have seen that a similar problem has been reported, which has been directed to the use of the activity for airplane mode or for data connection,but at the moment I don't have any profile or activity, why does tasker keep asking me for root permissions every hour?

Update - Fix: check draw over top and change system settings in app info. If missing, give those permissions.

------ op ------

Get this error everytime I try to run a task with autotools dialogs.

22.58.25/E FIRE PLUGIN: AutoTools Dialog / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 7 bundle keys

22.58.25/E AutoTools Dialog: plugin comp: com.joaomgcd.autotools/com.joaomgcd.autotools.broadcastreceiver.IntentServiceFire

22.58.25/E add wait type Plugin3 time 10

22.58.25/E add wait type Plugin3 done

22.58.25/E handlePluginFinish: taskExeID: 3 result 3

22.58.25/E pending result code

22.58.25/E add wait task

22.58.35/E Error: null

I'm going mad and can't pinpoint the issue.

Honor View 20, Magic 3.0.0, Android version 10.

I was ADB authorising Tasker, Join and Autovoice for Android 10 and since then my Android system switches the Keyboard input methods between my keyboard, Tasker and Join, making typing virtually impossible as the keyboard minimises every few seconds.

I have tried the basics of uninstalling, reinstalling, re-authorising, trying different keyboards installs but nothing holds. I can't find any other similar issues online so it must be something very specific I have done but not sure where to start. Any suggestions would be appreciated.

When I go to the scenes tab and tap the plus sign, I'm prompted to name my scene. As soon as I tap the check mark after naming, Tasker crashes. Backed up data, reinstalled, and restored. Same result.

When copy pasting a scene element, the dimensions always change slightly. (e.g. a rectangle of 50x50 becomes a rectangle of 54x47).

If you immediately change the dimensions (before closing the element edit scene), then the changes will not save. You have to open the element again and change the dimensions.