-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot write files #927
Comments
I'm experiencing (almost!) the very same error, but my device is a Android 12 tablet, BLU M10L Plus. Apparently some applications fail to create its own data directory under /storage/emulated/0/Android/data on this tablet for no reason at all, causing weird crashes or failures like this one, and yes, this means Shizuku is unusable on this device. But unlike the OP, I get a ENOENT because the directory doesn't exist:
FWIW, I'm using also a 128GB MicroSD card as application storage, but moving apps between SD and internal storage make no difference. Manually creating the moe.shizuku.privileged.api folder using the internal Files app turns the error into a EACCESS, as expected (since the directory is not owned by the app). I don't have a clue on what could be failing on this tablet, since some apps CAN create their own data subdirectories! Short of trying a factory reset or getting rid of the SD card for app storage (which I do not want to do as this tablet only has 32GB of internal flash), I'm running out of ideas here. |
Please report bugs of Shizuku itself.
Requirements:
Change "[ ]" to "[x]" if it meets the requirements.
Reports not meet the requirements will be immediately closed.
Information:
Logs:
Related full logcat.
**Describe the bug:**Cannot write file after re-entering shizuku
A clear and concise description of what the bug is.
Additional context:
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: