Partial success at best, constant permission popups at worst. Part 4: The Good News – Tasker’s Workarounds João is a wizard. Within weeks of the API 29 requirement, he implemented several powerful workarounds. You don't have to abandon Tasker; you just have to adapt your methods . Workaround #1: The "Use Document Tree" Mode (SAF) The most important feature you need to know: Storage Access Framework (SAF) .
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. tasker api 29
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. Partial success at best, constant permission popups at worst
Instead of saving a text file yourself, use an intent to open a "Save as" dialog via a file manager. Part 5: Specific Task Fixes (Copy-Paste Ready) Let's fix the broken examples from Part 3. Old (Broken) Backup Script: A1: Read File [/sdcard/Documents/notes.txt] A2: Write File [/sdcard/Backups/notes_backup.txt] Text:%text Fix: You don't have to abandon Tasker; you just
A Tasker user since 2012, owner of over 200 profiles, and survivor of the great API 29 migration of 2020.