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 have recently updated my system rom and Gapps packages. The new clock app is now slightly different (which is very cool and with assistant now integrated). It seems tasker has stopped recognising when my alarm is done and my profile is not triggering any more. Any fixes for that?

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

I would like to to see an option to use accessibility service to create scene. This will make scene to remain visible when other apps are showing overlay. 

I have a feature request for Tasker (or AutoNotification, whichever is more suitable): Could you add ability to control NotifificationListenerService's listener hints? https://developer.android.com/reference/android/service/notification/NotificationListenerService#requestListenerHints(int)

This feature allows users to mute notifications sounds and/or calls without being in do not disturb mode all the time. Idea is to use this when the smartwatch is connected, so the user's phone is not needlessly ringing when the smartwatch is already buzzing the user's wrist.

I know the same thing can be done with do not disturb mode, but then it perpetually shows do not disturb icon in the statusbar plus do not

If you were starting now, Tasker would be much better, with namespaces to avoid clashes of global variables, task names etc. We are not starting now, so have to manage with what we have. If a Tasker project is imported, and one of its tasks already exists in an existing project, the task is not imported. This is a good safe default. But a warning popup to tell the user that this had happened would be very useful. A task in the new project might use perform task intending to run one of the author's task and instead run some

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)

Hello,

It would be fun to have embeded feature to define specific DNS servers. It allows to set up DNS servers following conditions like specified connected wifi networks or radios, and so on...

Thank you

Hello,

It would be fun to add "android.permission.BIND_VPN_SERVICE" to tasker app. This will allow to send intent to VPN manager application to connect or disconnect following defined conditions.

Thank you

With the following task, if lines three to five are not deactivated, then the error shown below will pop up when the tasker editor is started, if you edit the task. That is, just open up the task, don't change it, close it, close the tasker editor, open the tasker editor and the error dialogue shown will pop up. There is no need to run the task to get the error message. Lines three to five actualy work fine, you just get an error message every time you edit the task.

Fortunately I have discovered a work around which is

Put the reason why the event occurred in the event parameters. I'd like to customize my Monitor task for the various reasons this event occurs; phone boot up, Tasker enabled, new version of Tasker installed, system update, etc. 

I have installed a number of different "voices" on my phone. In my case Samsung ones, but it might be Google ones. I did this for an air traffic control game, so that the pilots did not all sound the same. The game lets you choose from all the different installed voices.

I would really like to be able to select different voices to be used with different SAY actions.

If there's no answer when a get voice action is launched, Tasker crashes instead of continuing to next action.

That's important to me, as I'd like to use voice control to acknowledge being alive and safe in mountain, and if not, I might not be able to answer, the lack of answer repeatedly 3 times would be the signal to send sms to rescue team.

It can work only if get voice action doesnt make Tasker crash in case of lack of answer

Thanks for your help

I would love to be able to move the screen/content, for example to ignore notches and punch holes. This action would allow to use the whole screen regardless of any cutout.

Some elements could be not accessible anymore, that's why it's important to be able to do it quickly and be able to set it per app basis. It's the responsibility of the user to set this up and to use it. There should be a warning, that user could make the device not accessible if they use wrong numbers.

Thank you very much.

As we can use caller name or number as LOCAL variable. Can you add last missed call number and name as local variable? 

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.

Conditionals don't support this way of checking, although it's needed sometimes. Checking for %VOLM, for example. At some point your volume is neither greater, nor less than some value, and your flow stops, you need to make one more check for equality.