WARNING: Could not write to (...), using /tmp instead
See original GitHub issueInformation
- Apktool Version (
apktool -version
) - 2.4.0 - Operating System (Mac, Linux, Windows) - Linux (from ArchLinux AUR packages)
Steps to Reproduce
- Install
apktool
on new PC (or delete~/.local/share/apktool/framework
) - Run any decompilation, like
apktool d app.apk
Expectation
Any local folder and files should be created if missing like other programs.
Fix warning by yourself
mkdir -p ~/.local/share/apktool/framework
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Should I be concerned about this message "The object store is ...
The warning indicates that your docker container doesn't have enough shared memory, so it will use /tmp folder. This shouldn't cause any ...
Read more >Unable to write to /tmp directory in macOS ... - Super User
Reboot your Mac into recovery mode. Open Utilities menu in the top bar > open Terminal csrutil disable. Reboot. Remove the tmp folder...
Read more >tempnam - Manual - PHP
If the directory does not exist or is not writable, tempnam() may generate a file in the system's temporary directory, and return the...
Read more >DOCKER container with postgres, WARNING: could not open ...
Simple and dumb. I've tried another way: leaving the temporary file in container, where you need not deal with user permissions - and...
Read more >How do I fix the errors “Unable to write in the cache directory ...
These issues can be addressed by setting the correct permissions that will let processes read and write the tmp/ folder. General solution: if...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
How the hell did this not break tests, this is maddening.
Thanks for finding this.
For me on Ubuntu 18.04, this issue still exist even after giving full permission (777) to apktool and apktool.jar.
I gave full permission to the created directory to fix the warning.
Not exactly best practice, but it worked.