Tasker Api 29 Apr 2026
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.
Permission denied if the destination wasn't a Tasker-owned folder. 2. The Cross-App Data Mover You used Tasker to move a downloaded PDF from Download/ into a specific app's folder (e.g., /sdcard/WhatsApp/Media/WhatsApp Documents/ ). tasker api 29
Hard crash. You cannot write to WhatsApp's private directory. 3. The Bulk File Lister You used List Files on /sdcard/Android/data/ to see what game savedata you had. But fear not
Instead of using raw file paths ( /sdcard/Folder/file.txt ), you can use . You grant Tasker permission to a specific folder (like a tree), and Tasker can then read/write anywhere inside that tree. You cannot write to WhatsApp's private directory
Google heavily discourages this for store-distributed apps. It works, but you must do it manually every time you reinstall Tasker.
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.
A Tasker user since 2012, owner of over 200 profiles, and survivor of the great API 29 migration of 2020.