Tasker Beta 5.1.3b

[joaomgcd]

Hi everyone. This is my first time publishing Tasker! Pretty excited about it! :)

Some notes:

• I'll be using Google Play Beta publishing from now on, so please sign up for it here if you're interested: https://play.google.com/apps/testing/net.dinglisch.android.taskerm
• By signing up to the beta you'll get beta releases whenever they're available on Google Play. No more manual downloading.
• For now, app factory betas still have to be downloaded manually. Get this version here: http://appfactory.dinglisch.net/releases/AppFactory.5.1.3b.apk
• This beta has no functional changes from the previous version. It serves only to know if my build process works correctly since it's different from the original one that Pent used.
• If all goes well I'll release a new beta in a few days with some new features

Let me know how this works! :)

[Nathan Banks]

Hi João,

Build works fine for me!

You might want to add that people need to be a member of this Google Group to be eligible to join the beta. This post was added to Reddit on /r/Android and there has been some confusion.

Reddit link: https://www.reddit.com/r/Android/comments/83we7a/tasker_beta_513b_now_on_the_google_play_beta/

[joaomgcd]

Hi João,

Build works fine for me!

Great to know! :) Thank you!

 

You might want to add that people need to be a member of this Google Group to be eligible to join the beta. This post was added to Reddit on /r/Android and there has been some confusion.

Reddit link: https://www.reddit.com/r/Android/comments/83we7a/tasker_beta_513b_now_on_the_google_play_beta/

Thanks for that. I've now made the beta public so that everyone can join. No use on restricting the users really. 

[Raul SC]

Beta version installed. At the moment, my projects work without problems.

I have only verified that when installing the Beta version, I had to re-grant accessibility, device administrator and access to notifications.

Oh, one more thing, I had two Tasker Tasks widgets, which showed an error. It has been fixed by deleting and re-adding the widgets.

A greeting.

[thecu...@gmail.com]

The beta installed perfectly for me, from Google Play.

[joaomgcd]

I have only verified that when installing the Beta version, I had to re-grant accessibility, device administrator and access to notifications.

Thank you for the report. That has never happened for you before when installing a new version?

 

Oh, one more thing, I had two Tasker Tasks widgets, which showed an error. It has been fixed by deleting and re-adding the widgets. 

Hmm, that's not good. Don't want everyone to have to re-add their widgets. Can you detail what kind of error it showed? thanks!

 

 

[joaomgcd]

The beta installed perfectly for me, from Google Play.

Great to hear thanks! 

[joaomgcd]

I think I found an issue that might be causing the issues mentioned here. Could I please ask anyone's that's trying this beta to NOT re-do any settings if they can until I can release another beta? That way I can check if stuff continues working for you after my fix with no needed changes from the user. That'd be great thanks! :)

I plan on releasing a new beta tomorrow.

[Reinaldo Ornellas]

Salve João, parabéns aqui do brasil

Save João, congratulations here from Brazil

[Peter Bongé]

After installing the Beta the app shortcuts of the Tasker icon don't work anymore. I just get "App not installed".

And the notification action buttons don't work too.

[Bill Blandford]

Quick Settings tile still launch the task. But the Task name and icon never apply to the tile. Just stays as Toggle or Unset with black circle icon. Thanks.
Replicated on stock Pixel 2 and Nexus 5x on ABCrom, both on 3/5/2018 security update.
Unset https://imgur.com/a/h0ryo
QS https://imgur.com/a/fVsii

[Bill Blandford]

I was able to replicate the Notification Action Buttons not launching the tasks on pixel 2 and Nexus 5x both on 3/5/2018 security

[Bill Blandford]

me
I was able to replicate the App Shortcut Tasks not launching on pixel 2 and Nexus 5x both on 3/5/2018 security. They say Permission Denied.

[Bill Blandford]

I joined the Play Store beta today and upgraded my Tasker (originally purchased on Play Store in September 2012) to the beta on Play Store.

[Bill Blandford]

One more thing that may be helpful.
When I updated to the beta the Tasker app disappeared from the Nova folder I had it in, Also the Frozy icon pack doesn't recognize the beta as Tasker anymore.
Suspect something with package name may be off?

[Raul SC]

Thank you for the report. That has never happened for you before when installing a new version?

 

Sometimes the "accessibility service" is deactivated. It is not frequent, and neither had it coincided that it is just after installing a new version.

Regarding the options of "device manager" and "access to notifications", at no other time had it been deactivated. 

Hmm, that's not good. Don't want everyone to have to re-add their widgets. Can you detail what kind of error it showed? thanks!

Sorry, I have not copied the error code. I can only indicate, that instead of the icons of the widgets, an error message was shown.

When I tried to press on one of them, a flash came up with an error, but as I said, I have not copied it ...

If you need the error code, I can uninstall Tasker, reinstall it, and install the beta version, to see the error again.

Tested from a Xiaomi MI5S with Android.7.0 

[Judah Richardson]

Thanks Joao! This is all very exciting stuff :)

[Morgan Young]

I had the issues stated above as well. I will wait to see the next beta before I make changes.

[paradoxe]

Hi,
Just installed the beta and now, I have the following error on each SAY command.

Thanks

09.18.53/Variables doreplresult: |It is %TIME2 minutes past %TIME1. %Message| -> |It is 18 minutes past 9. Enjoy your day!|
09.18.53/Variables doreplresult: |%Language| -> |com.google.android.tts:eng-gbr|
09.18.53/Variables doreplresult: |%LanguagePitch| -> |5|
09.18.53/Variables doreplresult: |%LanguageSpeed| -> |6|
09.18.53/E onUtteranceCompleted: Say: .speechStart id: null err: false
09.18.53/E Say: spec: com.google.android.tts:eng-gbr contains :
09.18.53/E Say: engine: com.google.android.tts locale data: eng-gbr default engine: false
09.18.53/E set TTSStatus to -34234 by doSpeech: init
09.18.53/E Say: start init loop
09.18.54/E Say: oof: status; 0 elapsed: 186
09.18.54/E Say: tts engine: com.google.android.tts voice data: eng-gbr loclang: eng
09.18.54/E tts: loc eng_GBR available: 1
09.18.54/Mirror net.dinglisch.android.taskerm.MyUtteranceProgressListener: unavailable
09.18.54/E setProgressListener: Attempt to invoke virtual method 'java.lang.Object java.lang.Class.newInstance()' on a null object reference
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService$12.run(Unknown Source)
09.18.54/Mirror net.dinglisch.android.taskerm.MyUtteranceCompletedListener: unavailable
09.18.54/E setCompletedListener: Attempt to invoke virtual method 'java.lang.Object java.lang.Class.newInstance()' on a null object reference
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService.a(Unknown Source)
09.18.54/ net.dinglisch.android.tasker.ExecuteService$12.run(Unknown Source)
09.18.54/E Say: failed to register completion/progress listener
09.18.54/E Say: not started, shutdown
09.18.54/E result: stop task (error)
09.18.54/E Error: 1
09.18.54/MacroEdit action finished exeID 1 action no 30 code 559 status: Err next 30

[joaomgcd]

New Tasker.5.1.3b.bf beta is uploaded to Google Play and should be available in less then an hour for download. Let me know if that fixes the issues!

[Peter Bongé]

At least all my problems seem to be fixed now:

- App shortcuts are working again.

- Notification buttons are working again.

- App icon problem is gone.

[João Dias]

Awesome :) Great to know! Let me know if any issues not present in previous versions do come up. Thanks!

--
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/ICAS7pzQo0E/unsubscribe.
To unsubscribe from this group and all its topics, 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.

[Bill Blandford]

All issues I reported are now working as expected in newest beta 5.1.3b.bf
-Icons and title on QS tiles are there
-Notification Action Buttons launch tasks
-App Shortcut Tasks work after a device reboot (when coming from 5.1.3b the reboot was needed)
-Package is now recognized by Frozy icon pack as Tasker again.
Thanks so much!

[João Dias]

That's a relief that it's starting to work again for everyone :)

[Maher Tayara]

I got the same problem after downloading this beta and the last one from Google play.
Tasker get out from the folders where he was
Tasker shortcuts on screen disappeared
I'm on Samsung s6 android 7.0 stock launcher

[João Dias]

Thanks, but did you re-create those shortcuts  while on the previous version? That would cause the behaviour you're seeing.

[paradoxe]

It does solve the problem! :o)

Thanks a lot!

[Maher Tayara]

Yep I did because they disappeared so that's it
Good work
And I would ask if there are any other changes in this update (I didn't found a changelog on website)

[Raul SC]

I just updated to version 5.1.3b.bf

The icons of the widgets have disappeared again. No error message appears when I click on them.

After installing the beta version have been disabled again "Device Manager" and "access to notifications"

"Accessibility services", has not caused problems and continues to be enabled.

The widgets, I added them yesterday after installing the previous beta version. I just read your message where you clarify that this is the reason for the error.

[João Dias]

There's no more changes for this version :)

Thanks everyone for confirming!

The release notes for the upcoming version are here. Did Pent use to have a separate changelog just for betas?

--

[1337 357]

Experienced crashing issues on P DP1 on Pixel 2, no crashes yet on the latest beta. I'm sharing details from the logs anyway in case it's relevant:

[13787.377358] c0    609 type=1400 audit(1520948916.231:247): avc: denied { read } for pid=6459 comm="android.taskerm" name="leds" dev="sysfs" ino=28957 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:sysfs_leds:s0 tclass=dir permissive=0
[13792.014143] c1    609 type=1400 audit(1520948925.418:248): avc: denied { read } for pid=6459 comm="android.taskerm" name="vmstat" dev="proc" ino=4026532116 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:proc_vmstat:s0 tclass=file permissive=0
[13792.014170] c1    609 type=1400 audit(1520948930.055:249): avc: denied { read } for pid=6459 comm="android.taskerm" name="devices" dev="sysfs" ino=28835 scontext=u:r:untrusted_app_25:s0:c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0

Also:

03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime: FATAL EXCEPTION: main
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime: Process: net.dinglisch.android.taskerm, PID: 3601
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime: java.lang.RuntimeException: Unable to start service net.dinglisch.android.tasker.MonitorService@f0567d8 with Intent { cmp=net.dinglisch.android.taskerm/net.dinglisch.android.tasker.MonitorService (has extras) }: java.lang.NullPointerException: Attempt to invoke virtual method 'void net.dinglisch.android.tasker.PhoneStateListenerCommon.setHandler(android.os.Handler)' on a null object reference
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3665)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.app.ActivityThread.access$1600(ActivityThread.java:193)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1654)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:106)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:164)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:6656)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void net.dinglisch.android.tasker.PhoneStateListenerCommon.setHandler(android.os.Handler)' on a null object reference
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.K(Unknown Source:49)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.c(Unknown Source:186)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.x(Unknown Source:82)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.y(Unknown Source:17)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.aG(Unknown Source:5)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.b(Unknown Source:103)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.a(Unknown Source:191)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.a(Unknown Source:1)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.restart(Unknown Source:78)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.l(Unknown Source:392)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.a(Unknown Source:123)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at net.dinglisch.android.tasker.MonitorService.onStartCommand(Unknown Source:0)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3646)
03-13 09:45:39.619 10161  3601  3601 E AndroidRuntime:     ... 8 more

[João Dias]

Thank you. I'm glad the latest beta fixed that.

[Logan Fury]

Good Evening Joao,

Big Congratulations on your first beta release! Its a privilege to help with Tasker in any way and ive happily joined the beta group you linked. Looking forward to future downloads! 

[joaomgcd]

Good Evening Joao,

Big Congratulations on your first beta release! Its a privilege to help with Tasker in any way and ive happily joined the beta group you linked. Looking forward to future downloads! 

Thank you very much. :) You can always check out what's coming up here.

[Jay M]

swap the actionbar with a support library toolbar for us Android TV users 😁

--
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 ︻芫══一

[1337 357]

I started a thread with Android P DP1 compatibility issues, something for you to be aware of:

https://groups.google.com/forum/#!topic/tasker/ELnjRJDVbxU

[Alexey Rahlin]

After installing this version, i had to recreate desktop shortcut to tasker(nova launcher), also had to reenable accessibility service.

[Logan Fury]

Probably because of identifying data in the new release its recognized as a different app by Nova and required these one-time steps? It sounds more like something to be expected than worried about to me :)

On Thu, Mar 15, 2018 at 12:15 AM, Alexey Rahlin <ral...@gmail.com> wrote:

After installing this version, i had to recreate desktop shortcut to tasker(nova launcher), also had to reenable accessibility service.

--

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/ICAS7pzQo0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.

[João Dias]

After installing this version, i had to recreate desktop shortcut to tasker(nova launcher), also had to reenable accessibility service.

That's probably because you installed the previous beta first and created a shortcut with that right? 

[Gilles P]

New bug found 

When using function "send intent" of plugin "IntentTask" I'm getting the following crash:

13.20.33/TD getStatic: Active load: true
13.20.33/Plugin PLUG setMetaData: start: type: Action code: 1291811855 pkg: com.balda.intenttask clsOrLabel: com.balda.intenttask.ui.FireSendIntent
13.20.33/Plugin PLUG setMetaData: end: type: Action code: 1291811855 pkg: com.balda.intenttask cls: com.balda.intenttask.ui.FireSendIntent label: Send intent
13.20.33/Variables doreplresult: |%priority| -> |100|
13.20.33/E no wait key, next action
13.20.33/Plugin PLUG setMetaData: start: type: Action code: 1291811855 pkg: com.balda.intenttask clsOrLabel: com.balda.intenttask.ui.FireSendIntent
13.20.33/Plugin PLUG setMetaData: end: type: Action code: 1291811855 pkg: com.balda.intenttask cls: com.balda.intenttask.ui.FireSendIntent label: Send intent
13.20.33/E handleNewTask: fromUI: false
13.20.33/E onStart: ignoring new abort-type task JinaCB, already in queue
13.20.33/E 
        A1: [X] Send Intent [ Action:%par1 Cat: Mime Type: Data: Extra: Extra: Extra: Package:com.mobeedom.android.jinaFS Class:com.mobeedom.android.justinstalled.PluginsHelperActivity Target: ] 
        A2: Send intent [ Configuration:Send %par1 to Activity Timeout (Seconds): ] 

13.20.33/E child rejected
13.20.33/E Error: 1
13.20.33/MacroEdit action finished exeID 8 action no 0 code 130 status: Err next 1

Note: for this specific usage, since I don't need extra features, I can use the native Tasker Send Intent  function instead

[joaomgcd]

Which version of Tasker are you using? Thanks

[Gilles P]

Which version of Tasker are you using? Thanks

5.1.4b.bf3 

[joaomgcd]

5.1.4b.bf3 

Thank you. Do you get the same error on other plugin action types? 

[Gilles P]

Thank you. Do you get the same error on other plugin action types? 

I havent' noticed another yet (I've enabled option "popup/errors warning" to help to catch those errors)

[João Dias]

And do you always get the same exact error each time you try to run the action?

[Gilles P]

And do you always get the same exact error each time you try to run the action

Just noticed it's not systematic

Going to be uneasy to fix

[joaomgcd]

Have you ever gotten it on actions other than that one?

[Gilles P]

Have you ever gotten it on actions other than that one?

I guess without being totally sure: even if I'm using that plugin in few other tasks, I noticed that issue very recently, It's not easy to get the whole picture.

I get those messager relatively often when opening Tasker, so your autonotification plugin seem to be involved too:

[Maher Tayara]

I have the last version 5.1.4b too but because he posted here
The same problem even that I don't have any active profile for autonotification (I have 1 but inactive)
There is another after-update problem with autotools action which show error but doesn't stop execution (I think so because I get the same results from that tasks) but I couldn't catch it. I will try and repost.

[Maher Tayara]

I got it but like what I said I didn't see any change in the results and the tasks are not stopping.
BTW I keep getting an "Low in memory" error.

[Maher Tayara]

Sorry I didn't uploaded the photo so that's it

[joaomgcd]

Thanks for all the reports.

I'll post another update soon that will hopefully fix the plugin issues you're having, thanks!

[Mayank Thakur]

I am not able to get location in %LOC. I have attached taskers log and runtime log, please help me out here i was making an app from my profile which gets location on sms trigger and replies the current location and other properties but just %LOC is being sent.

[João Dias]

Did you use the "Get Location" action beforehand?

On Tue, May 22, 2018 at 5:32 PM Mayank Thakur <mack...@gmail.com> wrote:

I am not able to get location in %LOC. I have attached taskers log and runtime log, please help me out here i was making an app from my profile which gets location on sms trigger and replies the current location and other properties but just %LOC is being sent.

--

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.

[Mayank Thakur]

Thanks for your reply joo

i used it a long time ago but it never worked from the time i started using it in my app (about 2 month ago).

the task in which i use get location action is  

Start_tracking (45)
        Stay Awake
        A1: Variable Set [ Name:%Current_Operator To:%SMSRF Recurse Variables:Off Do Maths:Off Append:Off ]
        A2: Get Location [ Source:GPS Timeout (Seconds):100 Continue Task Immediately:Off Keep Tracking:On ]
        A3: Ringer Volume [ Level:7 Display:Off Sound:Off ]
        A4: Send SMS [ Number:%Current_Operator Message:
Location : %LOC
Battery : %BATT
Cell id : %CELLID
GPS Status : %GPS
Uptime from last boot : %UPS sec
Time : %TIME
Last called : %CONUM
Tracking process started Store In Messaging App:Off Continue Task After Error:On ]
        A5: Wait [ MS:0 Seconds:0 Minutes:2 Hours:0 Days:0 ]
        A6: Perform Task [ Name:Logger Priority:%priority+1 Parameter 1 (%par1):SMS TRACKING Parameter 2 (%par2):%LOC Return Value Variable: Stop:Off ]
        A7: Goto [ Type:Action Number Number:2 Label: ]
        A8: Flash [ Text:%LOC Long:Off ]

What am i doing wrong?

[João Dias]

Can you try using Get Location with Network and see if that works?

--

[Mayank Thakur]

Thank you very much!!

It worked, why didn't i thought of it earlier but is it as efficient as gps? 

what is the problem with the gps is it a bug or is it just me?

I also want to report another problem i ran into today the mobile in which i am using tasker does not have front flash so i am not able to see the Flash Mode option in Take Picture action and the generated app is set to "auto flash mode" (even when i use Discreet mode) and i want it off. what should i do for that? right now i am backing up my project and editing the "arg8"->"1" for that specific Take Photo action and then i have to quickly create the app after restore before applying anything or else the option is restored to "auto". The Flash Mode option is coming in Rear Camera.

again thanks for helping

[Alexander Fischer]

Hello,

many thanks for your good work. After updating to Android 9 the scan for near cells is not working anymore (also not with new api). Do you know something about incompatibility between Tasker and Android 9?
Kindly regards,
Alexander

[João Dias]

Hi there. I have tried it just now and it seems to work correctly for me. What device do you have?

[Ville Viitaharju]

Tasker icon cannot be hidden. It always reappers even while settings are correct. This happened after latest update.

[João Dias]

Thanks. I'll try fixing it for the next release!

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

--

[Judah Richardson]

You can hide it using the notification settings in Oreo+. I think it's always visible because of the "run in foreground" change. 

--
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/ICAS7pzQo0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.

[Ville Viitaharju]

You can hide whole notification there. But you can't choose to hide only the icon.

I still want that notification there, as it's quick way to access tasker. But I do not wan't that icon on top bar to show always.

[Judah Richardson]

Ah, I see. 

[João Dias]

Actually, you can hide the icon there. Set the notification to low importance :)

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

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.

[Manfred S]

had a bad experiance today in the morning. my mobile was blocked because of tasker. after reset it was blocked also. last chance was to start in secure mode and deinstall tasker. then the mobile was ok. would like to install the version before this update.
br

[João Dias]

Thanks for the report. Was there ever an error that came up that you could report so I can check out the error?

[Zekrifon]

On Monday, 12 March 2018 08:21:47 UTC-4, joaomgcd wrote:
> Hi everyone. This is my first time publishing Tasker! Pretty excited about it! :)
>
>
> Some notes:

> I'll be using Google Play Beta publishing from now on, so please sign up for it here if you're interested: https://play.google.com/apps/testing/net.dinglisch.android.taskermBy signing up to the beta you'll get beta releases whenever they're available on Google Play. No more manual downloading.For now, app factory betas still have to be downloaded manually. Get this version here: http://appfactory.dinglisch.net/releases/AppFactory.5.1.3b.apkThis beta has no functional changes from the previous version. It serves only to know if my build process works correctly since it's different from the original one that Pent used.If all goes well I'll release a new beta in a few days with some new features

> Let me know how this works! :)

Hello,

After I installed the latest update, I got two extra notifications from Tasker that won't disappear.

The notifications say Long click to disable you don't need these.

When I do long click it gives the option to minimize the notification. But I already did that.

I attached a screenshot.

What can I do to remove them?

Thanks.

[Robert Burton]

In Android>Settings>Apps>Tasker>Notifications you can turn off the Placeholder setting and any other Tasker notifications that you don't want to see.

[Zekrifon]

Awesome I didn't know that!
Thank you very much!

[João Dias]

I need to use a better text in the notification :) It works different on different devices/ROMs...

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

On Thu, Nov 22, 2018 at 4:22 AM Zekrifon <youssef...@gmail.com> wrote:

Awesome I didn't know that!
Thank you very much!

[Manfred S]

I sent you a report yesterday.
The content was:

net.dinglisch.android.taskerm version 5.6.1b.bf flavor: market

OS Buid R16NW.N950FXXS5CRJ6
OS Code 26
OS Target 26
Device SM-N950F
Manufacturer samsung
Product greatltexx

android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground()
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1881)
at android.os.Handler.dispatchMessage(Handler.java:105)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6940)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)

13.00
Context.startForegroundService() did not then call Service.startForeground()
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1881)
android.os.Handler.dispatchMessage(Handler.java:105)
android.os.Looper.loop(Looper.java:164)
android.app.ActivityThread.main(ActivityThread.java:6940)
java.lang.reflect.Method.invoke(Native Method)
com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)

[João Dias]

Hi, thanks, but can you please update from Google Play again? thanks

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Manfred S]

tried it. same result. tasker hang in a loop Ithink. It eat my accu (10% within 20min).
the mobile is blocked until I disable tasker

[jose.sch...@gmail.com]

I think there might be a bug with the newest update. If a profile is not active and I flag a command to only activate if the profile is active it will still run the command even if the profile is not active.

I have a profile that activates
if WiFi is not connected and on. it will run a wait time then shut off WiFi if the profile is active for 60 second. If the WiFi connects to something then the WiFi process should not run the off command. However with the newest update it still runs the off command even when the profile is not active. This has started with the newest update. Please roll it back.

[João Dias]

Hi there, thanks for the report! Can you please try this version? https://drive.google.com/file/d/1Ylh_yIG5dFtcBzWOjKs__TMDu9hZQWjd/view?usp=sharing

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[José Scharon]

What seems to be happening is that the command will work as intended for first use but after it will break and stay active even if the profile is not. 

[João Dias]

Can you please export your profile's description (not xml) so I can take a look? Long-click the profile in Tasker->export description Thanks in advance

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[José Scharon]

It worked before the update today. 

    Profile: Disconnect WiFi (19)
    Restore: no
    State: Not Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ]
    State: Variable Value  [ %WIFI ~ on ]
    Application: Not Pokémon GO
    Enter: Disconnect WiFi (20)
    A1: Wait [ MS:0 Seconds:0 Minutes:1 Hours:0 Days:0 ] 
    A2: WiFi [ Set:Off ] If [ %PACTIVE ~ *Disconnect WiFi* ]
   

[João Dias]

You have selected Restore:no in the profile's settings? Is that not the issue?

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[José Scharon]

If I enable restore settings it will re enable WiFi over and over again. 

Here is a screen shot. 

In the first screen shot you can see the profile is not active because the flags are not all triggered. WiFi is not connected but it is also not enabled. So the profile does not enable. However in screen shot two you can see that the command set WiFi off if profile is active is flagged as being true even though the profile is not active and it should be reporting as not true. The idea behind my script is if these actions are met WiFi is to be turned off. However for some reason after the update the command that tells WiFi to turn off stays true even if it's not true. 

[José Scharon]

Another Discovery. For some reason my profile won't activate. All it is, is if these applications run torn on location services. 

    Profile: Auto Location (12)

    Application: Pokémon GO, Maps or GPS Location Fix

    Enter: GPS On (14)

    A1: Location Mode [ Mode:High Accuracy ] 

    A2: WiFi [ Set:On ] 

    

    Exit: GPS Off (16)

    A1: Wait [ MS:0 Seconds:5 Minutes:0 Hours:0 Days:0 ] 

    A2: WiFi [ Set:Off ] If [ %PACTIVE ~ *Disconnect WiFi* ]

    A3: Location Mode [ Mode:High Accuracy ] If [ %PACTIVE !~ *Auto Location* ]

    A4: Stop Location [ Source:Any ] If [ %PACTIVE !~ *Auto Location* ]

    A5: Location Mode [ Mode:Off ] If [ %PACTIVE !~ *Auto Location* ]

    

[João Dias]

Can you please try with the new beta version 5.6.1b.bf5? Thank you!

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Me Too]

Hello,

Is there more help on using autolocation info. I can't get image map file working.

Thanks 

Mesh

[Ben Marriner]

Hi. Getting a pretty big issue since the last beta update. Error message saying my trial has expired and I need to purchase Tasker through Google Play. Signature verification failed.

When I open it through Google Play, I get the error again after a couple of seconds.

Please help!

[Robert Burton]

You're posting on an old beta thread but you may need to give Google a little time to get the licensing updated. It has happened once before and took about an hour. Also, have you tried restarting your phone.

[Robert Ryan]

I have the same issue. Google's licensing is sometimes slow to update. The last time this happened it corrected itself within a couple of hours. 

[João Dias]

Should work now. Sorry for the inconvenience.

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias