We need to call number 2*1500 to sign in to our phone network, and 2**1500 to sign out.

Very similar numbers, as you can see.

Tasker seems to be a bit confused about this. Trying to add two tasks - one when calling 2*1500 and another when calling 2**1500

The solution was to have contacts with these numbers (that we had already) and then in Tasker use the name of the contact instead of the number.

In reference to my previous post i may have the answer.

Back in the days when i created profiles and their relative tasks i was using the app with the language set to english and i still prefer to have english as default. Now, from time to time tasker decides on its own (???) to change language to italian (which is the OS language) and that causes all of my tasks to stop working properly. When i change language back to english everything seems to work again as normal. How do i prevent tasker from automatically switching languages?

Thank you

I have a speaking clock profile that announces the time on the half hour. The first action is a display on or I should say Turn on with default block time 500ms. I have another profile mute media volume using the Samsung bixby button. Again the first action is Turn on but it doesn't turn on. Could it be the secondary app context or the app I'm muting or something else?

When Tasker is placed on the home screen, and Tasker Secondary is not on the home screen. When applying a change in Tasker. Then Tasker is replaced by Tasker Secondary on the home screen.

Attachment: - TaskerShortcutIsReplacedByTaskerSecondaryOnHomeScreen.mp4 Video reproducing the behavior.

Tasker Version: 5.9.2 Phone: Samsung Galaxy XCover Pro Model number: SM-G715FN One UI version: 2.0 Android version: 10

Hello, 

I bought a Google Suite account to replace my former Gmail account, but apparently this disabled my Tasker licence. 

¿Could you please transfer my licence from my Gmail to my Google Suite account?

Many thanks, regards

Jorge 

Hello. I think Ifound a bug. When Profiles first action is NFC-tag and if NFC ID is not defined then in native Tasker it works fine, but if you Export to APK application, then this application says No Active Profiles. If you write NFC ID in NFC-tag action, then APK application works fine.

Device is Oneplus 8 Pro on Android 10. The Display -> Turn On task does not work. I've tried increasing the "block" value but no change in behaviour. Thanks.

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?