r/tasker • • Nov 11 '18

Google is taking away SMS/MMS and Call functionality from Tasker

2.0k Upvotes

UPDATE

SMS And Call Permissions: A New Hope - Tasker will probably get to keep these permissions after all!

[[Update] - SMS and Call Permissions: One Step Closer] (https://www.reddit.com/r/tasker/comments/9xrcj8/update_sms_and_call_permissions_one_step_closer/) - Another update!

Keeping the original post below for posterity.

The Problem

So google recently announced some changes to how Google Play store handles SMS and Call permissions in apps. I'm all for more security, so I submitted the requested form convinced that even though an app like Tasker doesn't appear on that list of exceptions, they could acknowledge that automation apps are a perfectly fine example of apps where these permissions should be allowed. Let's see:

  • Tasker requests for the SMS and Call permissions only when strictly needed

  • The user has to explicitly use SMS and Call conditions and actions in Tasker for Tasker to do anything with them

  • Tasker doesn't log or keep any of that data anywhere outside its own runtime environment unless the user chooses otherwise

For Tasker to have access to this data, the user has to go out of their way to give Tasker that access. Nevertheless, 40 days after I submitted the request (giving me only 50 days to make necessary changes, including the Christmas holidays) they respond with this:

Thank you for contacting the Google Play team. We have received the following information in the Permissions Declaration Form you submitted:

Q1 - Core use case(s)Caller ID, spam detection, and blocking, Cross-device call or SMS sync & send, Initiate a text message, Initiate a phone call, Automation of an unlimited number of situations based on calls, SMS and MMS

Q2 - Declared permission(s)READ_CALL_LOGWRITE_CALL_LOGPROCESS_OUTGOING_CALLSREAD_SMSSEND_SMSWRITE_SMSRECEIVE_SMSRECEIVE_MMS

I’ve reviewed your request and found that your app, Tasker, net.dinglisch.android.taskerm, does not qualify for use of the requested permissions for the following reasons:

  • The declared feature, "Initiate a text message, Initiate a phone call, and Automation of an unlimited number of situations based on calls, SMS and MMS" are ineligible for these permissions.

  • The declared feature "Caller ID, spam detection, and blocking and Cross-device call or SMS sync & send" are allowed; however we determined it to be unnecessary for the core functionality of your app.

  • The declared feature "Caller ID, spam detection, and blocking and Cross-device call or SMS sync & send" are allowed; however we were unable to verify this feature during app review.

  • Your app has default handler capability that doesn’t match with your declared feature.The default handler features are allowed; however your app does not appear to prompt the user to be a default handler prior to requesting related permissions as required by the policy.

Please follow the steps below to submit an updated app.

Next steps

  • Read through the Permissions policy and review the Use of SMS or Call Log permission groups help article, which describes exceptions, invalid uses, and alternative implementation options.

  • Make appropriate changes to your app. Remove the specified permissions from your app’s manifest, migrate to an available alternative, or evaluate if your app qualifies for an exception.

  • If your app is a default handler or you believe your app qualifies for an exception, please submit a new request via the Permissions Declaration Form to use these permissions.

  • Make sure that your app is compliant with all other Developer Program Policies. Additional enforcement could occur if there are further policy violations.

  • Sign in to your Play Console and submit the update to your app.

  • Alternatively, you can choose to unpublish the app.

If you've reviewed the policy and have further questions, please reach out to our policy support team.The Google Play Team

In short, Tasker is ineligible for these permissions. The Automation app use case doesn't apply here.

Extra Security

As I said, I'm all for security, but please give users what they want. Maybe Google can have a big popup when an app requests these permissions saying BE VERY AWARE! THIS APP CAN ACCESS ALL YOUR SMS! ONLY GIVE ACCESS IF YOU TRUST THE APP!, or they could make it a special permission, like Device Admin, or Accessibility Services, anything! Anything but to take away stuff from users and developers that they have worked so hard for!

SMS is one of the most used features in Tasker, but because someone at Google forgot to make it an acceptable case for these permissions, now everyone loses.

I mean, this is still the operating system where ANY APP can simply access the user's clipboard without requesting ANY PERMISSION AT ALL! Clipboard: the place where millions of users routinely put their passwords in...

Again If Google really is concerned about privacy, please give users the chance to defend themselves. Don't simply take stuff away...

This has happened before

Tasker was previously banned from Google Play because it requested the permission for Android to not optimize battery for it. After a few days, Google reconsidered and unbanned the app. Google added a special exception in their policies because of Tasker (Task automation app in the list). Maybe the same will happen here? It would be great but in the mean time a lot of user and development time will be lost trying to deal with the situation.

Another similar situation was when Google announced they would remove apps from Google Play that used accessibility services for anything other than helping users with "disabilities", which besides being incredibly vague (what exactly is a "disability") makes no sense because those can be used for a lot of purposes. So, Google later simply forgot all about it. Again, Google actually listened to users and devs, but in the mean time a lot of time and money was lost.

Let's seriously hope that Google can reconsider this situation as well!

TL;DR;

There you have it. Until further notice I'll have to spend the following month making the app ready to be used without SMS and Call permissions. As if I don't have anything better to do at the moment... :P Please expect SMS and Call functionality to be removed from Tasker in January. If you don't like it, tell Google about it!

PS:

In their email above Google says Alternatively, you can choose to unpublish the app. However, during a recent Google Play Q&A session their representative said that devs even need to make their unpublished apps compliant. So, which is it Google??

Please upvote on r/android and /r/androiddev


r/tasker • • Nov 08 '15

[PSA] TASKER on AMAZON APP STORE IS FAKE. Do NOT DOWNLOAD Tasker from AMAZON.

607 Upvotes

Do NOT DOWNLOAD Tasker from AMAZON.

Somehow someone masquerading as "Crafty Apps EU" has put a FAKE version of Tasker on the Amazon App Store for purchase.

DO NOT PURCHASE OR DOWNLOAD TASKER FROM AMAZON.

It may be malicious malware spyware, etc.

When the issue is resolved and a true version becomes available from Amazon, this PSA will be updated or removed or - a new post made confirming the version on Amazon is authentic.

Some discussion took place here on the matter over the weekend, and this information is confirmed by Pent (Tasker's developer).

 

For the true and official / authorized version of Tasker download it from the Google Play Store.

 


r/tasker • • May 21 '16

We at XDA are considering adding a Tasker repository to the XDA Labs app, let us know your thoughts!

458 Upvotes

edit: Thanks for showing so much support! I'm sure that all this outpouring of agreement will be able to convince the rest of the XDA team to get on board with this idea!

Hey /r/Tasker,

You might know me as the Tasker guy from XDA. I got permission from the mods here to post this so I wanted to float this idea around with you guys to gauge interest.

I've been pushing for our XDA Labs app to include a section for Tasker scripts since I'm a major user of Tasker myself and I have a lot to contribute.


Here's a mock-up of how it would look in the app.


Planned Features

  • Anyone can upload scripts from the online labs web console by signing into their XDA forums account. We will host all of the files.

  • We believe we can automatically pull the title and the icon mentioned in the XML file (by storing the Tasker icon packs server side) so all that users would need to add on their own would be a description and a screenshot. Before we launch it though we want to finalize exactly what kind of metadata should be present so let us know if you think there should be any other data included.

  • Users will be able to sort scripts by rating and be able to leave feedback on these scripts directly, much like our app interface.

  • Although Tasker does not directly import scripts, we captured the intent that makes Tasker move the script into the proper directory so you can quickly auto-import it when you launch Tasker.

  • Other features TBD.


Why am I here?

So far I've gotten our lead editor and the main app programmer on board with the idea. But we want to convince everyone else that this is worth pursuing so we're hoping to see some support from potential users.

Is this something you are interested in?

IMO this would be better than sharing files on personal file hosting sites that could expire or reach download limits, plus it would be easier to sort and search.


r/tasker • • Oct 02 '19

Tasker helped with a medical emergency today!!

429 Upvotes

So today when I was out, I had a panic attack and fainted. I was fortunate to be near people who immediately flocked to my location. A paramedic was only 5 minutes behind them.

They were concerned as nobody could feel my pulse. I was apparently freezing cold and limp, too.

Paramedic gets the phone out of my pocket and goes into ICE (In Case of Emergency).

AutoInput detects this and triggers a whole array of profiles.

It first speaks allowed they have activated ICE and asks them for their name. This then is logged and sent, along with my GPS, to my partner and select friends, with AutoLocation providing nearby Landmarks as well as a GMaps link.

AutoVoice at this point goes continuous and listens for key words; name, pulse, breathing, emergency etc.

When it heard the paramedics stating they couldn't feel a pulse and before they attached the oxidiser, my phone quipped "Subject heart rate is at <heartrate>", thanks to AutoWear.

Tasker then changes some QuickTiles to allow the emergency response to automatically phone (and put on loudspeaker) ICE contacts.

I come-to in the ambulance and the paramedics first statement was "Whatever you're running on your phone, you need to sell to everyone!" I laughed, replying "Weird way of telling me I'm dead!" 🤗

May just have some NHS nerds buying Tasker soon! Was showing them all of the antics it can do.

Now, I do want to share this project (I did on G+ before it became too integrated), so do bare with me whilst I try to make a more universal version of it (it contains quite a lot of my personal data).

Principal

AutoInput detects ICE screen being launched from Lockscreen.

Task Activates GPS, AutoLocation and AutoVoice continuous and some additional profiles just for this case.

AutoVoice recognise (from continuous only) for specific keywords.

Pulse/breathing will trigger an AutoWear screen to get pulse and read it aloud when got. Name will tell them my name and age. If it hears "emergency, breathing and pulse" within the same profile activation, will SMS my partner everything AutoVoice hears. It also allows her to text back and it be read aloud. It'll also read aloud my pulse every 60 seconds until stopped manually.

QuickTiles are changed to make a loudspeaker call to 1 of 5 ICE contacts.

QuickVideoRecorder is also triggered by SMS, so misses can send an SMS to stop AutoVoice and film for 30 seconds. This is then uploaded to my server where she can view it.

It's amazing how a simple idea can be a big help.

If it wasn't for Tasker, who knows how this would have played out. I even got Tasker to lie for me so they'd discharge me. _Made an OK Google shortcut to IFTTT.. I've been watching his BPM and O2 levels. He just needs to go home, have a hot bath and a large dose of CBD and sends a notification to Tasker. TTS then sent to watch stating "subject bio rythms are stable, shutting down emergency monitor" - they seemed to believe my tech more than me!

The thing is, is that my pulse watcher profile actually alerted me to the panic attack before it happened; it detected my heart rate spike from a modest 87bpm to 190bpm < 60 seconds. But, I ignored it.

Just another day with anxiety and AS for me 😊

Considering Tasker is in no way designed (or even really should be depended on) for an emergency, it just goes to show it has the potential. And this project is by far anything close to mature, or even reliable. Was actually in disbelief it did what they said it did; misses forwarded me the texts to confirm.

Thanks to all behind Tasker; Pent, João, plugin developers and ofc the awesome community that makes Tasker epic fun to learn and use. It just goes to show beyond a shadow of a doubt that Tasker is by far the the most powerful tool for Android to date and serves not just mundane Tasks, but potentially life saving ones.


r/tasker • • Mar 03 '23

Developer [DEV] The time has come: ChatGPT can now be used in Tasker!

375 Upvotes

Full Demo: https://youtu.be/TwN2oLKNI88

OMG, I've broken my assistant! 😆😆 https://youtube.com/shorts/n8UUvf4NnyY?feature=share

Yesterday OpenAI finally made their ChatGPT API public so naturally I had to use it with Tasker!

I've created a project on TaskerNet that you can import so that you can easily use ChatGPT in Tasker yourself.

Import the project here.

Please read the full TaskerNet description of the project so you understand what it needs to work and how it works.

I love the task to summarize my WhatsApp notifications myself and creating a nasty assistant is hilarious! 🤣

Can't wait to see what you can come up with and what new ways this will be used now!

Enjoy!


r/tasker • • Nov 15 '18

[Update] - SMS And Call Permissions: A New Hope

349 Upvotes

Background

You may be aware of the great SMS and Call permission debacle from a few days ago. Well, I've got some good news for you! :)

There are humans!

Someone at Google's policy team got in touch with me yesterday, and we had a brief call about the whole situation.

Yes, there are people on the other side! Best of all, they recognize that they need to change and adapt more to developer and user needs!

They are learning

The Google rep said that it's a learning process for them. They came up with the rules that they thought were able to

  • keep "bad" apps from abusing permissions

  • keep "good" apps working

Obviously they missed some use cases :)

The great news is that the rep really took my feedback to heart, and was really sad that people think that their side is just a bunch of bots replying back to developers automatically.

I suggested that someone on their team could for example browse /r/androiddev and respond to devs there once in a while, just to let people know that the policy team actually has some humans in it. :) That would already make a world of difference and would keep both devs and users much less frustrated.

Their intention is not to turn Android into iOS like many, many people mentioned. They were aware (or at least they are now) that stuff like automation apps is what sets Android apart from competitors.

They said that they're working to update their Help Center page and the permissions declaration form to increase clarity and speed for developers affected by the policy changes.

The rep could not guarantee that there would be a special exception for automation apps ( she would have to go through the feedback with her team first), but from the conversation I'm very confident that Tasker will be accepted as an exception once I resubmit the updated form.

Thank you!

I also wanted to thank you! Everyone that commented here on reddit and that starred and commented on the issue in Google's issue tracker. You're the reason that Google reached out to me in the first place :) Without all the fuss around this issue, this (apparently) positive outcome wouldn't have been possible! So thank you!

TL;DR;

It looks like Tasker will be able to keep the SMS and Call permissions after all! I'll have to resubmit the request form, but judging from the conversation I had with a Google rep, the outcome should be positive. Also, they are taking previously rejected apps under consideration again, so there's hope for all legitimate use cases!

I'll keep you posted on any news on this issue!


r/tasker • • May 03 '15

The other day my auto texter messaged Chipotle back and forth 1772 times until my phone died

322 Upvotes

r/tasker • • Nov 06 '19

Developer [DEV] Tasker 5.9.beta.8 - The Game Changer

303 Upvotes

I'm sooooo excited for this one!! 💥😁💥

Sign up for the beta here: https://play.google.com/apps/testing/net.dinglisch.android.taskerm

If Google Play is taking to long, get the APK directly here: https://www.dropbox.com/s/7j58vurja7vm4hj/Tasker.28.apk?dl=0

Opening up a world of events/states with the "Logcat Entry" Event

Tasker now has the ability to react to the Logcat on your device! 😎 Check out how it works in this demo video: https://www.youtube.com/watch?v=3GSE1q6q_Q4

If you're not familiar with it, Logcat is a place where Android and all its apps put logs of stuff that's happening in the apps and now Tasker can react to it!

Just to give you a few examples of stuff that was done with it in the short time I tried it:

A whole new world of events is there ripe for the picking! Since I've implemented I just kept coming up with more and more possible events that Tasker can now react to and more often than not there's something in the Logcat that will do it!

I'm super excited to see what the community comes up with! I'm sure there's A LOT of stuff in there that you can react to that I haven't thought of yet!

Would love to know what you can come up with! :)

Replacing AutoShortcut with the new "Shortcut" action

I really should stop shooting myself in the foot. 😝 After implementing stuff from AutoLocation and AutoAlarm in Tasker itself, AutoShortcut can now probably be deprecated as well with the new action.

Here's a demo of it working: https://www.youtube.com/watch?v=pcZWcnQfzDM

Just like AutoShortcut it allows you to launch an Android shortcut from Tasker!

You also get a new related Tasker Function called ShortcutDialog() that allows you to select a shortcut from Tasker so that it can later be used with the new Shortcut action.

Previewing Variables

When you're in the Variable Select list in Tasker you'll get the option to long click a variable to know its value.

Check out the demo: https://www.youtube.com/watch?v=HYR9wFktWfI

Getting the best location possible

I've added an option in the Get Location v2 action that allows you to get the last gotten location even if the action times out.

For example, let's say you want to get your location with an accuracy of 10 meters but your phone can only bring that down to 15 meters. With this new option the action will still time out but you'll get that 15-meter-accuracy location in your task so that you can decide if you still want to use it or not.

Long Standing Bugs Fixed

I've fixed 2 very old bugs:

  • sometimes a task would hang if another task was running at the same time and a wait action was running there

  • when you monitored the value of %LIGHT and the light level sank to 0, %LIGHT would never actually be 0 but would remain in the value previous to 0

I'm happy to say that these are both fixed now! :)

Full Changelog

  • Added "Logcat Entry" event which allows you to react to any logcat on your Android system

  • Added "Shortcut" action which allows you to open an Android shortcut from Tasker

  • Added "ShortcutDialog()" function in "Tasker Functions" action that allows you to pick a shortcut so that you can run it later

  • Added option in "Get Location v2" to get last available location if action times out. This way you can at least still get a decent location even if it doesn't match your criteria

  • Added ability to long click a variable in the Variable select list to show its value

  • Added ability to specify a directory as the output for a HTTP Request action so that the file name is automatically recognized and set when downloaded

  • Added %http_file_output variable as output in the HTTP Request action so that you can act on the downloaded file more easily when the file name is automatically found by Tasker

  • Changed "Get Location 2" name to "Get Location v2"

  • Changed all prefixes for the variables from "Get Location v2" to "gl" instead of "cl"

  • Changed some variable names for both "Get Location v2" and "Pick Location"

  • Changed some messages that show up as toasts into dialogs so that people that block Tasker notifications still see them.

  • Fixed long-standing bug (from back when I wasn't the developer) that would sometimes hang a task if another task had a wait action running

  • Fixed long-standing bug (from back when I wasn't the developer) where if you monitored the value of %LIGHT and the light level sank to 0, %LIGHT would never actually be 0 but would remain in the value previous to 0.

  • Fixed some issues where changes in Light could adversely make some profiles stop working

  • Allow scenes to manually specify horizontal offsets higher than normally supported

  • Added Custom Settings for the Pixel 4

  • Changed Cell Near history to 24 hours instead of 6

  • Fixed bug where importing a project with disabled profiles would sometimes enable them

  • Fixed HTTP Request action when downloading a file to a folder that doesn't exist. Now creates needed folders automatically.

  • Made some events trigger faster with less use of resources

  • Fixed "Alarm Changed" event in some situations.

  • Fixed getting the clipboard on Android 10 in some situtations.

  • Correctly ask for Do Not Disturb changing permissions when adding the Ringer Volume action

  • Fixed small crashes

I hope you enjoy this one and do let me know what you can come up with with the new Logcat Entry Event! 😃

Edit:

Just updated to beta.9 with a few fixes:

  • Made Load Last App available for everyone again! :)

  • Fixed issue where Tasker monitor would sometimes restart over and over again if Reliable Alarms was set

  • Tried fixing reporting next alarm changed

  • Moved "Shortcut" action to "App" category

  • Removed error toast when cancelling shortcut picking dialog

  • Fixed giving the app READ_LOGS permission automatically on rooted devices

  • Added ability to use regex filtering in Event "Logcat Entry" by adding ~R at the start of the filter (same as for every event)

  • Added option to filter by "Different Than" speed and altitude in "Get Location v2"

  • Fix not being able to accept the "Get Location" action if you checked "Continue Tracking"

  • Fix small crashes


r/tasker • • Nov 20 '17

Request [Request] I'm 43 with Dementia - looking for help to set up some automation - in order to stay living on my own longer

302 Upvotes

tl;drI have Dementia and need to automate some processes

I have a ridiclously-named degenerative brain disease called Lewy Body Dementia. It's not like a 90-year old grandma type _ It's the same disease Robin Williams had. Troll my post history or hit LBDA org for more info.

Essentially, my brain is in a constant state of degeneration - think of it as random links on the internet break each second. This continues until there is no internet left - in my case, I should die in the next couple years due all kinds of system failures.

My goal is to live independently for as long as I prefer/can and then take the long walk (the state in which I reside allows death with dignity - basically you can get a prescription and you don't wake up).

Enter Tasker - I'm familiar with it and worked with it a bit many years ago (along with one of those first Kickstarter smart watches). The problem is my cognitive decline makes it exceedingly difficult to learn new things and the short-term memory loss makes performing anything complex frustrating and it takes me so much longer to do anything now. It's like I had the latest 16-core multi-threaded CPU and now I have a Pentium 100.

I'm looking for someone(s) to give me a hand in setting up my phone/auto/house. I'm not looking for crazy complex stuff - just the basics.

This will save what brains I do have left to concentrate on having an awesome time in my last days. We can figure out compensation for the time.

If anyone lives in the PNW, even better.

Thanks Tasker community

Edit January 5, 2018 - fixed link and made new reply with update


r/tasker • • Apr 29 '19

Tasker 5.7 is rolling out for everyone!

291 Upvotes

The beta version is now stable and is finally rolling out for everyone!

Note: This is a staged rollout which means that it will not become available for everyone at the same time. If all goes well, over the next couple of days everyone should have access to the newest version. App factory update will be done after the Tasker rollout is at 100%.

Here's the Release Video!

And for anyone that's new to Tasker, you should really watch this video to get you started: https://www.youtube.com/watch?v=s6EAbLW5WSk

Check out the huge changelog for this version here. A lot of stuff to go through there. :)

Here's the main new stuff added to Tasker:

  • New Say WaveNet action! Allows you to use much more realistic voices for your say actions. Demo.

  • New Keyboard action! Simulate keyboard keys. Allows you to navigate app's UIs (using the arrow or tab keys for example) and interact with inputs in other apps! Demo.

  • New Navigation Bar action! Totally customize the bottom navigation bar with custom icons and commands (on supported devices). Demo.

  • New NFC Tag event and action! Allows you to react to NFC Tags and write data to them! Demo.

  • New Volume Long Press event (Android 8+) which allows you to handle long clicks on the physical volume keys on your device even when the screen is off. Demo.

  • New Secondary App launcher icon and Secondary App Opened Event. This will allow to perform tasks from other places like double-tapping the power button or Bixby. This icon can be hidden if not needed.

  • Tasker and App Factory now target API 28 (Android Oreo). This doesn't mean that the apps will stop working on older devices. Just that they are now more inline with the latest Android best-practices.

  • New Notification Settings action. Allows you to open an app's notification settings screen with an optional category (useful for App Factory apps)

  • New Notification Channel Info action which returns all info about a given notification channel for Tasker or the kid app that's running

  • Added Notification Channels for all created notifications (user and system). Disable the ones you don't want to see in Android Settings.

  • New option in menu: Report Issue To Developer so that users can more easily send the developer a log with for issue they're having with an optional video and audio capture to make it easier for the bug to be found!

  • Made all Global Accessibility actions (Back, Quick Settings, Power Dialog, etc) able to work without the Tasker accessibility service being on, if Tasker has the WRITE_SECURE_SETTINGS permission

  • Made Turn Off action work on Android versions < 9

  • Do not Disturb, ringer, system volume and Sound Mode actions now use Do Not Disturb permission instead of Notification Access permission on Marshmallow+

  • Fixed a long standing major memory leak that occurred when using the Profile Status action (and possibly other actions)

  • Run a lot of stuff in background threads so Tasker should be a lot snappier now.

Here are Taskernet links for most of the examples seen in the release video:

This marks a huge milestone for Tasker because, on top of all of the new features above, I was finally able to handle all the restrictions that Android imposes when targeting the latest Android APIs. It has proven to be quite a challenge on an app like Tasker that basically tries to deal with everything available to the Android OS. :)

Hopefully I'll be able to make releases much more frequent now, now that the target API hurdle has been overcome. I actually already have a bunch of new stuff coming up already after this version has proven to be stable for everyone ;)

Enjoy!! 🎉😁🎉

PS: I now have a page over at Patreon. Check it out sometime! :)


r/tasker • • Dec 20 '15

Tasker saved me from a very upset girlfriend. Here's how...

284 Upvotes

Currently, I'm the only one with a key to our apartment, but that's another story. We recently lost the other set and need to replace them. Anyhow, girlfriend came home from work at 12:30AM after a one hour commute (works in a hospital). She fully expected me to be awake, as did I, since I always wait for her and I'm generally a night person anyway. Well I fell into this deep, heavy sleep sometime between 9 and 10. I was seriously out. Despite being an otherwise light sleeper, I didn't hear my phone when she called for me to open the gate.

I have a profile set for these situations. Two, in fact. One triggers a really loud ringtone at maximum volume when I miss 3 calls from her within a 3 minute period (this is what triggered tonight) and the other one triggers the same sound when she texts me "EMERGENCY". Fortunately I have both ways trigger the same response because she had forgotten about the time I told her she can text me that keyword to wake me up or alert me in an emergency.

Whew! The wrath of her would have been ugly had she had to wait in her car outside for me to eventually wake up and realize she's not in bed.

Thanks, Tasker!

Edit: Screenshot of two profiles. Both are triggered by the same event: missed call from girlfriend. One waits until the third call to ring the alarm while the other one resets after waiting three minutes (otherwise alarm would ring after third missed call in a week, month, etc.)

Edit 2: Not shown: SMS emergency response. The screenshot shows the two parts of the missed calls alarm.


r/tasker • • Jan 04 '19

[Update] - SMS And Call Permissions: SUCCESS!!!

270 Upvotes

Finally! Tasker has finally been approved to use SMS and Call permissions and not lose any of its functionality!

Background

In case you aren't aware, there was a great SMS and Call permission debacle a while ago because Google said that Tasker couldn't use SMS and call permissions anymore, meaning it would lose the ability to interact with SMS and calls on your phone. A few days later Google got in touch with me, trying to make things right. Then, after a while they added Device Automation apps to their exception list.

Final Confirmation

Now, finally, after all this time they sent me the following email:

Hi Developers at joaomgcd,

Thanks for contacting the Google Play team.

We’ve approved your use of the following permissions in your application, Tasker, net.dinglisch.android.taskerm:

  • Device Automation

  • PROCESS_OUTGOING_CALLS, READ_CALL_LOG, READ_SMS, RECEIVE_SMS, SEND_SMS, WRITE_CALL_LOG, WRITE_SMS

Your app has been approved to use the declared permissions solely for the purposes stated in your application and subject to Google Play’s developer policies. Any transfer, share, or license of Call Log or SMS data is restricted to the core purpose of the app. Call Log or SMS data may never be sold.

Please make sure that your app complies with all other Developer Program Policies. If you need additional help you can also visit the Play Console Help Center or the Android Developers website.

Thank you for supporting Google Play.

SUCCESS! Or is it?...

This stuggle is finally over for Tasker. Everything can proceed as normal. But other apps might not be so lucky (check out the background reading section in that post) which is a shame. I'm lucky that Tasker has a big enough audience that Google would contact me about it, but I would really hope they can revise some of the other justifiable use cases.

For example, Join still hasn't gotten approval to use all the needed permissions. There's no use in hindering apps that make legitimate use of these permissions, so it shouldn't happen at all. I understand that Google wants to create a safer ecosystem, but killing apps that make Android stand out from other OSes is not the way to go.


r/tasker • • Nov 30 '15

New App - "Join!" - has all Pushbullet functionality and more, no subscription.

264 Upvotes

 

New App - "Join!" - has all Pushbullet functionality and more, but with no subscription fees.

 

Seems that Pushbullet's recent move to make people pay $50/year has spurred developers to take up the challenge and provide a better (and free'r) alternative.

 

"Join!" is a stand-alone application, but of course also has Tasker integration. Features include:

 

  • Paste your PC clipboard on your Android device, writing the text directly, and not just keep it on your clipboard

  • Paste your Android device’s clipboard on any other Android device or PC with a handy floating bubble menu bubble copy

  • Send unlimited SMS messages from your PC

  • Send links from any device to any device

  • Send files from any device to any device

  • Take a screenshot on your device and open it on your PC

  • Google drive integration: Join doesn’t keep any of your pushes: it’s all safely kept on your personal Google Drive account so you can manage it (and delete it) whenever you want

  • Use the join icon in Chrome to bring up your devices or…

  • Handy Keyboard shortcuts in the Chrome extension:

  • Ctrl+Shift+K will show a popup with your devices where you can execute a command

  • Ctrl+Shift+L will execute the last used command on the last used device. So, for example, if the last thing you did was send your clipboard to your Nexus 6, using this will send the current clipboard again to your nexus 6

  • Easily use multiple accounts or let your loved ones join in on the action with the device share feature

  • Easily send content from anywhere you can make an HTTP connection with the easy to use Join API: long press a device in the Android app to generate a URL you can use.

  • Trigger Tasker tasks with the built-in AutoApps integration

 

Developed by João Dias /u/joaomgcd, creator of the AutoApps, Join! is currently in beta (video demo here), and more features will likely be added daily and weekly. IMO the best solution moving forward for all the features listed above without the need for any high priced subscription!

 

EDIT: Excellent Review/Article posted today on AP about Join!

 

 


 

UPDATE DEC 10, 2015

 

*Notification Mirroring - including sending the applications icon/image, actionable buttons for reply etc, along with a number bubble in the Chrome tray icon to show number of notifications unread/seen if you have stepped away from the computer.

 

*SMS Send/Receive with Contact Support & Sync - Inside a window that resembles the one you'd see on your device, with contacts / conversations / etc.

 

*Options to run Join commands from anywhere.

 


 

UPDATE JAN 12, 2016

 

*Windows 10 Client Now Available! Some visuals here and also release details including Notification Mirroring and sharing from the Windows 10 share system!

 

*Tasker Plugin capability allows Join functions from within Tasker to be initiated from any Tasker Action. Including using Tasker data and variables to deliver to any Join linked device: Text, Urls, Send an SMS remotely, and more!

 

*Official Join Icon Finalized and selected from hundreds of user submissions. This new icon is now present across all Join platforms and clients.  

 

*Just Months into development and Join is an absolute powerhouse!

 


r/tasker • • Dec 08 '17

How To [How To] My favorite simple task that I haven't seen here yet. Guests text me #WIFI and my phone automatically sends them my Wi-fi password.

263 Upvotes

PROFILE

Wi-fi Password Text

EVENT:

Received Text

Type: Any

Sender: left blank

Content: #WIFI

TASK:

1. Send SMS

Number: %SMSRF

Message: whatever your wifi password is


That's it. My friends get a kick out of that whenever they're over at my place and I show them that for the first time.


r/tasker • • Sep 22 '26

Developer [DEV] I'm back! I also have 1500+ requests to go through... 😅

259 Upvotes

Hi everyone! I'm back now, after a big break.

Unfortunately I do have a BIG backlog of requests to go through now, which is always the downside of long breaks 😅

Please forgive me if I'm not very active for the next 2 weeks or so, until I get rid of the backlog.

It's good to be back! 😁👍


r/tasker • • Dec 14 '14

TASKER 101: Tutorial for absolute beginners.

252 Upvotes

Step by step introduction to profiles, triggers, scenes and application workflow. Tasker can be little dificult to start with, I have been there and I remember what made me struggle most. Majority of online guides focus on ready made profiles, rather than giving you a knowledge base to start with. With a great feedback from Tasker Google Community I was suggested to share it on here as well. I hope you find it useful!

Happy Automating!

https://www.youtube.com/playlist?list=PLDoIcTNj_voWtehhVwi3-RsDnXne_pfjt


r/tasker • • Sep 16 '25

Developer [DEV] I'm back! Now I need some time to get back up to speed... 😅

250 Upvotes

Hi everyone! I'm back :)

I've been away for a bit now and visited some very cool places while I was gone, but now it's back to business as usual! 😁

I do have over a 1000 requests to go through though, so please give me some time to catch up to everything. Don't be surprised if I'm not much around for the next week or 2.

I did notice that the tutorial forums are down at the moment, (EDIT: They're back now!) but I already figured out what's wrong and I'm working on a fix now. Hopefully I can get them back up tomorrow.

Anyway, it's good to be back! 😀 Hopefully everything else went smoothly while I was away! Guess I'm about to find out... 😅

Cheers!


r/tasker • • Nov 29 '16

How can I set my phone to play the "Back to the Future" theme when I reach 88MPH?

240 Upvotes

Just like the title says, how can I get my phone to play the "BTTF" theme (assuming it's in my media library) When I reach 88MPH?


r/tasker • • Feb 01 '23

Developer [DEV] - I give up: The current Beta of Tasker won't be updated anymore on Google Play. Only when it goes out publicly to everyone in production will you see another update on Google Play.

228 Upvotes

As you may know from my earlier post I've been trying to update Tasker on Google Play for a while no, but unfortunately it's just not possible it seems.

I've had an EXTREMELY frustrating experience with Google support, just trying to be able to update the app, which I'd like to share with you today.

I'll be creating a separate post about a new Tasker update after this one so you can at least get new versions through Reddit and hopefully bring it up to par before releasing it publicly.

Here we go...

TL;DR

I can't update the app on Google Play in BETA because of a permission that the app already has in PRODUCTION. I'll release beta updates on Reddit only, until I can release it to production and things will go back to normal.

The REQUEST_INSTALL_PACKAGES permission

This permission allows apps to bring up the standard app install popup on your device, allowing you to install or update an app.

To be clear, this permission doesn't allow Tasker to actually install an app, just to bring up a dialog that asks the user if they want to install it.

Recently Google started restricting which apps are allowed to use this permission on the Google Play Store for security reasons.

Before they started doing this though (and this part is very important to the rest of the story), the permission already existed and apps on Google Play already were allowed to have them. Tasker already has this permission in Production in the publicly available version for a long while now.

In any case, the new restrictions are now in place so apps had to be updated and only those allowed to have the restriction could have it on Google Play.

Trying to use the permission in Tasker on Google Play

Reading the help page, some of the permitted use cases are:

  • Web browsing or search; OR

  • Communication services that support attachments; OR

  • File sharing, transfer or management; OR

  • Enterprise device management.  

  • Backup & restore

  • Device Migration / Phone Transfer

At first I figured Tasker would have no issue getting this permission since it pretty much do all of the stuff on the list save for "Enterprise device management".

To my surprise I updated the app on Google Play and even with this example video clearly showing one of the permitted use cases, the update got rejected:

https://imgur.com/n2tVuKu

Ok, maybe they didn't understand my video or explanation of why the permission is needed? I tried to appeal so they would check again, only to receive another email that was almost exactly the same but added this part:

https://imgur.com/L2r25qV

Ok, that is a bit more info... I thought that maybe I needed to update the app's description on Google Play so that it mentions when the app needs the permission. This has been the case for the Accessibility Service permission before, so I tried to update it and reply to Google:

https://imgur.com/YbeqAZV

After 5 whole days they simply reply with this (BTW, all their replies usually take 3-5 days):

https://imgur.com/HtQkCjj

I get back to them with this:

https://imgur.com/t8mwSqK

But they're not budging:

https://imgur.com/ugUGDPl

I won't get into many more details on this but I went back and forth with them and they basically always gave me the same answer.

I CLEARLY showed them a use case in Tasker that falls into one of the allowed use cases but they wouldn't reconsider it. I tried this for more than a month.

Oh well, you can't win them all I guess.

Thankfully I could still resort to Tasker Settings to at least be able to have the functionality present through that.

Ok Google, you win, I'll remove the permission from the Google Play version (I kept it in the direct-purchase version though 😁)

Removed the permission. Good to go... Right?

WRONG! 😆 (just so you know, they always sign with a specific name like Cami in this case, but it always feels like we're talking to bots)

What?? So even after I removed the permission and tried to update the app, I still couldn't do it? What was up?

I sent them this:

https://imgur.com/jzW8Tkb

"Cami" replied:

https://imgur.com/lwRpXri

"Planned implementation"?? 😂 What is that about?

I replied:

https://imgur.com/OxUP1S2

But the reply is as helpful as ever:

https://imgur.com/UqQOZ1f

At this point I knew I wasn't getting anywhere, so I waited for the "proper team" to respond! It worked! 😅

https://imgur.com/GhIecC7

Ok, now we're talking! This is the "proper team" after all! They'll be able to help and understand me for sure! I tried my best to describe the situation:

https://imgur.com/cvRPDKR

But again, they just reply with a cookie cutter response:

https://imgur.com/7GkMNiG

But there is ONE PIECE OF NEW INFORMATION THERE! 😮 It says that I need to do a 100% roll out of the app for it to work! Ok, maybe that's what's wrong? I reply:

https://imgur.com/Dv5jRjU

However "Sirius" was feeling a little botty that day so they replied with:

https://imgur.com/WIKgBHu

OMG 🤣 For one second I thought I could talk to him as if he were human, but the "staged rollout" keywords in my email clearly triggered the "staged.rollout.txt" reply script 😆

I still had a glimmer of hope that Sirius was a human so I replied:

https://imgur.com/E8KvSkp

But alas, it was all in vain:

https://imgur.com/bqdtud8

Alright, I've had enough. I'll just roll it out to 100% of users and deal with the consequences later.

IT STILL GOT REJECTED!

This time I got "Tristan"! Yey! Unfortunately it seems like Tristan is a close friend of Sirius judging by his response 😆:

https://imgur.com/U1bIAhx

So the problem is that I can't update the BETA because the PRODUCTION version already is live and already has the permission because it was uploaded before the new policy change!

To be fair, I was warned that this was going to happen but it was so unbelievable that I thought I could somehow get through to Google and show them how crazy this is so I had to give it a try:

https://imgur.com/Hy39mN5

Tristan got back to me with some promising instructions:

https://imgur.com/4p0NRU1

Except they don't work because I can't exclude a Production APK from a Beta release 🤣 That wouldn't make sense at all. It was a pre-defined response after all. I replied:

https://imgur.com/PuZInWi

This was clearly too much for Tristan. He couldn't handle such complex concepts. He got back to me with a sad goodbye:

https://imgur.com/tlM7WKh

Well, maybe I'm being redirected to someone that knows what they are talking about? Maybe a *gasp* REAL person will actually reply? This time I got "Mimi" (I like their names :P):

https://imgur.com/6yGXRDW

Holy crap! 🤣 Now they think I want to deactivate the production version of the app??? I got back to them:

https://imgur.com/7fnq8QR

Again, seems like Mimi is close friends with the other bunch:

https://imgur.com/sf4ylS5

Mimi?? I thought you were my homie!

https://imgur.com/UL0e6su

She got back to me, and what do you know it, she sounds a little bit human now:

https://imgur.com/3BGiJ44

She didn't seem to simply copy-paste a predefined response! SUCCESS!!! 🤣

Unfortunately she said that the production version of the app was rejected when it was not. It is clearly live right now AND it has the offending permission: https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm

So I sent my last reply at the time of writing:

https://imgur.com/8oBb6sf

I can't wait to see what Mimi says to that! 😆

Giving Up

It doesn't matter though. I'm fully convinced that the beta will never make it on Google Play.

To clarify, the whole issue is that the version in production has the REQUEST_INSTALL_PACKAGES permission because it was uploaded BEFORE they had the Google Play Policy in play, but now I can't update the app in BETA because of that.

So, I'll just be releasing betas from now on here on Reddit and not on Google Play. I'll make another post about a new release today.

It sucks though, because I have over 50k testers on Google Play which often pick up on little bugs that don't affect a lot of people and so I can fix them before putting the app out for everyone.

For example, the next Tasker update will have its Target API updated to API 31. Updating the target API is often a source of small bugs and inconsistencies and it would be awesome to be able to test it with a large user pool. Hopefully testing on reddit will suffice though!

In Conclusion...

I went through the trouble of creating this post because I wanted to show a little glimpse under the hood of what working with these issues is sometimes.

Don't get me wrong, having an app on Google Play is great, and I treasure it every day! I just wish it was possible to sometimes have someone on the other side that didn't simply press a button to send out a pre-formatted response.

It would also be great if the emails weren't signed by "Mimi" or "Sirius" or whatever, but instead flat out said that they were automated responses! At least we wouldn't get our hopes up with those! If only real people signed their emails we could at least manage our expectations and not waste our time talking to bots as if they were real people. This particular issue isn't even THAT important but I wasted so much time on this because I always felt like if I could just get them to understand what I was talking about they would not reply with pre-made responses for once and could finally help me out. It has happened before.

I just wanted to mention too that I insisted with Google for so long on this issue because for ALL other permissions that are hard to get (like the permission to MANAGE_EXTERNAL_STORAGE which seems to me to be a lot more sensitive then the one above) it was just a matter of insisting and insisting ad nauseum until someone at Google eventually understood that it made sense and allowed it. I was able to get it to work for all permissions until now.

Well, hope this was a good read at least... 😅


r/tasker • • Sep 15 '20

Developer [DEV] I'm back! But now I have to go through a lot of requests, so not really fully back yet... 😜

222 Upvotes

I'm back from my break! :)

In my time away I did a few things:

  • Helped my kids release an album

  • Learned 3D modelling in Blender and created this 3D Tasker intro :) (and also this little test). Plan on doing all kinds of small 3D animations for my videos.

  • Started to learn how to play the guitar (wanted to do this for a long time)

  • Thought about the future of Tasker and had a few new ideas

  • Spent a lot of time with my family

All in all, it was time very well spent!

Now it's back to work though: my least favorite part of it to start off, which is going through an endless list of support requests and reply to all of them 🤣. I have over 1000 to go through by my last count so please bear with me for these first few weeks.

Hope I can get back to development soon!!

Glad to be back! 😁


r/tasker • • Oct 25 '19

AutoVoice on Google Assistant has been taken down

222 Upvotes

EDIT - Temporary Workaround: https://forum.joaoapps.com/index.php?resources/integrate-google-assistant-with-tasker-using-join-ifttt.206/

EDIT 2 - It's up again but only English for now: https://www.reddit.com/r/tasker/comments/dp8q2u/autovoice_on_google_assistant_update_its_up_again/

EDIT 3 - It's up again for a few more languages (English,French,Dutch,Portuguese (Brazil),Russian)

EDIT 4 - It's up again for all languages! Check here: https://www.reddit.com/r/tasker/comments/k21ivu/dev_autovoice_is_back_on_the_google_assistant_in/

EDIT 5 - Now it's down again forever. Check here: https://www.reddit.com/r/tasker/comments/149wqo0/psa_you_can_no_longer_use_autovoice_with_google/

So a few days ago I tried to get a new version of the AutoVoice action for the Google Assistant approved. It's normally a complicated process so I was kinda expecting to be rejected and I was. Every time I try to update there are new issues to resolve and I was expecting this time to be the same.

To clarify, being rejected an update is not a big issue. The public version will continue working as before.

This is what Google sent me for that update request:

https://i.imgur.com/SSa0Unz.png

Ok, no problem. There's some issues to figure out, I'll get back to it later.

Then today I got this:

https://i.imgur.com/gT8rsYR.png

What? So it was not ok, but suddenly it was ok. Weird, but ok...

Then after about 10 minutes I got this:

https://i.imgur.com/t7mOhuV.png

Wow! So they approved a version that clearly had some issues in their opinion just to take a perfectly working version down a few minutes later because it contained some unapproved stuff THAT THEY HAD JUST APPROVED THEMSELVES!

Also, the issue they mention is just with the description. They even suggest the description I should use.

The current description I have is the following:

If you install the AutoVoice Android app and Tasker you'll be able to do anything you want with your Google Assistant.

Suddenly there's no more stuff that it doesn't understand because you can just make it understand anything you want. :)

Check this video for some examples of how it can work: https://www.youtube.com/watch?v=oFfOfCxukCs

The description they suggest is this one:

AutoVoice Action works along with the AutoVoice Android app. You'll be able to send commands from the AutoVoice Action to the AutoVoice Android App to perform several types of actions. Check this video for some examples of how it can work: https://www.youtube.com/watch?v=oFfOfCxukCs

Is this really a good reason to take the whole action down? Was it really such a huge issue that the action couldn't be up until the description was changed?

I already contacted their support but it says

We're currently receiving a high volume of support requests. If you're sending a support request, please expect delays in our response.

so I don't expect a swift response.

In the meantime if you try to use AutoVoice on Google Assistant you get this:

https://i.imgur.com/8N8exAk.png

"AutoVoice is no longer available".

This is both on an Android device and on Google Home.

I now expect 1 star app reviews galore while this issue is not resolved. Let's hope something can be done about this.

Just wanted to fill you in on the situation!


r/tasker • • Dec 11 '19

Developer [DEV] Tasker 5.9 now rolling out for everyone!

221 Upvotes

Finally, 5.9 is out! This is a huge release! Some (like me 😁) might event call it the game changer! Check out the release video!

https://www.youtube.com/watch?v=bINUcn0QXvg

Read all about it here: http://bit.ly/tasker5_9

If you don't want to wait for the Google Play update, get it right away here.

You can also get the updated app factory here.

Highlights:

  • Logcat Entry Event potentially adds thousands of new events to Tasker, like actions for unlocking your phone with different fingers for example!

  • AutoAlarm and AutoShortcut's functionalities are now fully integrated into Tasker

  • React to Media Buttons

  • Faster and more precise location with Get Location v2

  • Enable/Disable camera system wide

  • App actions with app name (instead of just package name)

  • and much MUCH more!

Check out the full changelog here: http://bit.ly/tasker5_9_changelog

It has started to roll out now, so expect to get it in the next 24 hours or so!

Enjoy! :)


r/tasker • • Mar 02 '18

Announcement Pent passing the Tasker baton to João Dias

221 Upvotes

r/tasker • • Jun 28 '23

How To [HOW-TO] Replace Google Assistant With ChatGPT!

215 Upvotes

Video Demo

Shorter Video Demo

Import Project

This project combines multiple projects to ultimately allow you to totally replace Google Assistant with ChatGPT!

You also have the option to only replace it when you say a certain trigger word in your command.

For example, you could make it so that it only calls ChatGPT when the command you say to Google starts with "Please" or something like that (thanks /u/Rich_D_sr 😅).

To summarize, this allows you to greatly expand what Google Assistant can do and give it super-powers by giving it generative capabilities!

Let me know if there are any issues!

Enjoy! 😁


r/tasker • • Feb 15 '20

Tasker Removed From Google Play

214 Upvotes

EDIT: Seems like Tasker is now back! Crisis adverted. Still shouldn't have happened in the first place.

I have a theory on what triggered this, but it's just a theory and I can't really prove it.

Take a look at these fields in the app submission form on the Google Play Dashboard:

https://i.imgur.com/CZfELZj.png

I had never noticed these 3 fields before:

  • Instructions for app review

  • Video instructions

  • Non-compliant APKs

My theory is that these fields are now mandatory for all Device Automation apps (possibly other types of apps that need the SMS/Call log permissions as well).

I had never filled them in so I'm guessing that what happened was this:

  • update to the Google Play Dashboard website added new mandatory fields

  • bot scanned for apps that didn't fill in all mandatory fields and removed those apps from Google Play

To make it perfectly clear, this removal was not triggered by a Tasker update. It just happened at some random time which makes my theory even more plausible.

Now I've put out an update that didn't update the APK but simply filled in those fields and Tasker is now back, so hopefully things can return to normal. I've lost half a day worth of purchases. Hope that doesn't bring Tasker down in the rankings on Google Play too much.

**********************ORIGINAL POST BELOW***********************

Link to Tasker on Google Play: https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm

Here I was enjoying a nice relaxing Saturday morning with my family when I got a notification from twitter alerting me to the fact that Tasker was not on Google Play.

Indeed, I checked my email and there this was:

Publishing status: Removed

Your app has been removed due to a policy violation. This app won’t be available to users until you submit a compliant update.

Issue: Violation of Permissions policy

After reviewing your app, we found that it doesn’t qualify to use the requested permissions for the following reason(s):

  • Unable to verify core functionality of appWhen you submitted your app, you specified your app's core functionality as follows: Device Automation. However, we couldn’t find evidence that the app offers the declared core functionality during our review. Please submit an updated Permissions Declaration Form that includes instructions on how to verify your declared functionality, and include details such as test account information. If portions of your app are restricted, please share a link to a video of your app to help us verify the core functionalities you’ve declared.

  • Missing runtime permissionsYour app needs to use runtime permissions for us to complete the review. Please update your app to target API level 26 or above. If you have non-compliant APKs in different tracks of the app releases section of your Play Console, please deactivate (for Internal Test track) or create an empty release (a release without any APKs) before submitting your app again.For additional guidance, please review the documentation on how to request app permissions.

Wow. Just wow...

So, arguably the most well known and oldest automation app out there is now no longer a Device Automation app.

Also, for some reason an app that targets API 28 and has implemented runtime permissions for nearly 2 years now, suddenly no longer does either.

As per Google Play Requirements When you upload an APK, it needs to meet Google Play’s target API level requirements. Both new apps and app updates must target at least Android 9 (API level 28) which means that it would've been impossible for me to have updated the app in the last few months, which obviously I have. A simple check of the last uploaded APK would check that.

In conclusion, I don't know what Google is on about. This makes absolutely no sense at all.

To make things worse I was in the process of building a new beta with new added functionality that I can't simply put out for everyone to use all of a sudden because nothing's been tested by users yet, so now, on a Saturday morning, I'm going to have to waste my time by trying to remove functionality from my app and hope that I don't break anything in the process so I can put it out for everyone to use...

I'm also losing any potential sales of the app until this is fixed.

Hope this gets resolved soon.