Tasker plugins errors

[John Smith]

I got this problem while executing tasks using various tasker plugins (AutoInput, Autoshortcut, SecureTask, KC Tasker processes). Sometimes they all work, sometimes don't. I have no idea why, it seems to be random. For example If I create a simple task using AutoInput for launching an app from the shortcut, and execute it manually - it works (green dot) and when I try the second time - it gives an error (red dot) and text like this:

17.46.10/E FIRE PLUGIN: AutoShortcut / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 7 bundle keys
17.46.10/E AutoShortcut: plugin comp: com.joaomgcd.autoshortcut/com.joaomgcd.autoshortcut.BroadcastReceiverRunShortcut
17.46.10/E add wait type Plugin1 time 5
17.46.10/E add wait type Plugin1 done
17.46.10/E add wait task
17.46.15/E Error: null

The same happens for all my tasker plugins, I see no clear pattern why sometimes they work good and other times don't.

[John Smith]

I found somewhat similar thread: https://groups.google.com/forum/#!searchin/tasker/error|sort:relevance/tasker/1wLjgcx-Z4g/woZ6x5U2CgAJ

But:
- I got newest 4.9u4 version
- Allow External Access is disabled (by default btw)
- I tried other solutions mentioned in above thread and nothing helped...

It seems to me like the first action performed by any plugin is done correctly, but the next ones fail with errors randomly.

[John Smith]

After hours of playing with different settings I found this:

Turning bluetooth ON disables all tasker plugins for about 1 minute (Xiaomi Mi5, MIUI 8.3/Android 7.0)

I'm using tasks that are switching BT on/off depending on situation. If bluetooth goes from OFF to ON state all my tasker plugins refuse to work and their actions freeze. After a minute all goes back to normal and frozen plugin actions fire all at once... What is going on? Please help me guys :)

[Martin gigli]

i'm having the same problem, in the last days all my plugin stop working, they do work by them self, but not with tasker. Any news about this?

[Martin gigli]

I'm can confirm that i have the same problem in two devices a nexus 7 2013 and a motorola x pure, both with last lineage 14.1. Both do the same i excute a plugin and does nothing, after let said 30 o 40 minutes the taskmay execute but tasker doesn't know.

[John Smith]

Thank you all for your overwhelming support, nevermind :)
After many years of using Tasker I just switched to Automagic. Now everything works flawlessly, no need for paid plugins...
bye

[Martin gigli]

I still have the problem, and i don't want to leave tasker. Any help please?

[Robert Ryan]

The trouble is that this is a very rare type of problem that could have any number of possible causes.

Without having some information that can narrow down the possibilities it is difficult to offer a helpful suggestion.

The first thing I would suggest is to whitelist all of the plug-ins so that they are not battery optimized. At this point though, I can only guess.

[Martin gigli]

Tasker and all the plugin are whitelist, whati have done already is to resinstall tasker and autoremote, without any result. I'm testing with autoremote and hue pro tasker because both have their own apps so i can test if they are working, both do.
I leave an autoremote log.

[Simon Chester]

I'm having the same problem, too: none of my tasks that reference plugins work reliably, usually throwing up an error like: 

12.34.48/E FIRE PLUGIN: AutoHue / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 10 bundle keys

12.34.48/E AutoHue: plugin comp: com.cuberob.autohue/com.cuberob.autohue.Receivers.FireReceiver

12.34.48/E add wait type Plugin1 time 5

12.34.48/E add wait type Plugin1 done

12.34.48/E add wait task

12.34.53/E Error: null

Particularly frustrating as Tasker controls my lights, stereos, alarm clock...

What's strange is that no updates occurred on my device before this started, so I'm wondering if it's a background Google services update or something?

[Jay M]

I have a task that shows an AutoTools dialog and it stopped working with the same error^ I opened the Autotools app and my dialog was there I closed it and another 3 popped up closed all of em went back to Tasker ran the task again and problem solved so try opening the app for whatever plugin is giving you grief.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

Jay M ︻芫══一

[Simon Chester]

Unfortunately, not that simple - there is no interface for those plugins outside of Tasker. 

When I go to configure them from inside a task, I can do a 'test command' and they work fine, but when I trigger them from a task, they don't work. 

I just flashed a new ROM on my phone (dirty flash - upgraded from 7.1 to 7.1.2) and the problem persists, too.

I have no idea what's happening here.

s_c

[ Tw | Fb | Li ]

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

--

Jay M ︻芫══一

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/B-HwBIU3J18/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Martin gigli]

yes the same here. If the problem had happened after the update I would said it was the rom, but this happend between updates.

[Martin gigli]

may i understand there is no fix for this? i ask because i need tu use the plugin, without them Tasker is rather useless.

[Jay M]

https://plus.google.com/+IanGrodyRules/posts/MduC3cA1vHM

On Sat, 3 Jun 2017, 17:15 Martin gigli, <martin...@gmail.com> wrote:

may i understand there is no fix for this? i ask because i need tu use the plugin, without them Tasker is rather useless.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Robert Ryan]

Downgrading to version 7.1.29.21.arm of the Google App seems to have solved my issues.

[Pent]

Thanks for the link Jay.

Pent

[Jay M]

npz i probably should of said something like theres a fix here <link> instead of just posting a link and saying nothing which is a bit spammy but hopefully it helps :)

On Sun, 4 Jun 2017, 12:34 Pent, <crafty...@gmail.com> wrote:

Thanks for the link Jay.

Pent

--

You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[joaomgcd]

My theory is that Broadcasts are somehow being limited, but how could the Google app do this? Any theories Pent?

[Pent]

My theory is that Broadcasts are somehow being limited, but how could the Google app do this? Any theories Pent?

I'm sorry, I havn't looked into it since I'm very busy with the 5.0 Tasker version, plus Tasker and the plugins havn't changed
so it's something Google has done (which is also backed up by the reports).

Can you reproduce it ? If you can, could you post a log when it fails ?

Most of my Google stuff is disabled and auto-updates disabled, probably why I havn't seen it.

Pent

[joaomgcd]

I cannot reproduce it at all on my devices which have the "offending" version of the Google App.

Other people are reporting that it has to do with a device being seen as "certified" by Google.

Yeah, but I wish I could reproduce it so we could get a bit more info out of it :/

[Pent]

Other people are reporting that it has to do with a device being seen as "certified" by Google.

What's a certified device ?

People who can reproduce this problem in the task edit screen with the play button: could
you post or send a log:

http://tasker.dinglisch.net/userguide/en/faqs/faq-how.html#x2

Thanks,

Pent

[João Dias]

I didn't know either, but apparently this: https://support.google.com/googleplay/answer/7165974?hl=en

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/B-HwBIU3J18/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[Pent]

Is there anyone here with the problem who doesn't have a custom ROM installed ? If
so, what is your device and Android version plesae ?

Thanks,

Pent

[Simon Chester]

Moto Z Play, Android 7.0, completely stock. 

Task worked again for about 24 hours, but broke again today. 

There's now a new Google app on the Play Store, which I just updated to.

I had disabled Tasker, but just re-enabled it and the problem remains.

I can get you a log, too, but don't have time at this very moment.

s_c

[ Tw | Fb | Li ]

--

[Robert Ryan]

Motorola Droid Turbo 2
Stock 7.0
No root

I had been experiencing significant delays with tasks activated by a profile. Sometimes the task wouldn't run at all. Fixed by replacing the Google App with the earlier version.

Is it possible that the Google App is intercepting the broadcasts and then "forgetting" to relay them to the rest of the system?

--

You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/B-HwBIU3J18/unsubscribe.

To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Eric]

I also have 

Motorola Droid Turbo 2 
Stock 7.0
No root

My plugins still work but it takes a long time for them to fire after connecting to bluetooth, about 30-40 seconds. I use AutoShare to press play after connecting to my car or speaker and the tasks will still run but with a long delay. After I have been connected to bluetooth for a minute or so the tasks and plugins run right away. I downgraded my google app and the problem went away. 

[Robert Ryan]

Interesting, I also first realized that I had a problem when my BT Connected profile stopped working. I had very much the same symptoms that you describe.

[Martin gigli]

i have a moto x pure with lineage 7.1.2 doesn't work and a sony z2 tablet with android stock 5.1.1, which works.