29: Tasker Api

A Tasker user since 2012, owner of over 200 profiles, and survivor of the great API 29 migration of 2020.

API 29 was a wake-up call. But Tasker survived. And so will your automations.

But fear not. We are going to break down exactly what API 29 means, why it happened, how it affects Tasker, and—most importantly—how to fix your broken tasks for good. tasker api 29

But here's the perspective: Google is trying to protect normal users from malicious apps that steal their photos, read their bank PDFs, and encrypt their files for ransom. Tasker is collateral damage in a war against malware.

The red errors in the Tasker log feel personal. They feel like Google telling you that you don't own your phone. A Tasker user since 2012, owner of over

Empty list, or only Android/data/com.joaomgcd.tasker/ (Tasker's own folder). 4. The SD Card Sorter You had a task that moved photos from DCIM/Camera into dated subfolders on an external SD card.

So why did this become a Tasker nightmare? Because . João Dias (Tasker’s developer) had no choice. He had to update Tasker to target Android 10, and with that came Scoped Storage . Part 2: The Villain – Scoped Storage Before Android 10, Tasker had free rein over your storage. It could read, write, delete, and modify any file in /sdcard/ (your internal storage). Want to delete a stray MP3 in your Music folder? Easy. Want to modify a JSON file in a game's data directory? No problem. And so will your automations

Google heavily discourages this for store-distributed apps. It works, but you must do it manually every time you reinstall Tasker.