AppManager
AppManager copied to clipboard
MuntashirAkon
Backup Volume is not available
- [X] I know what my device, OS and App Manager versions are
- [ ] I know how to take logs
- [X] I know how to reproduce the issue which may not be specific to my device
Describe the bug
App Manager 3.0.0 installed in a work profile (root granted). Upon start App Manager always shows this error message:
"The selected [backup] volume is not currently available. Change volume [button]"
Clicking the "change volume" button and selecting the only entry (internal storage user 10) does not fix this issue.
Backups also fail, I suspect because of this issue.
This is maybe caused, the new AppManager actually/absolutely need folder named "AppManager". Either in Internal storage or SDCard. AppManager not auto create the folder.
The Top description of Backup Volume setting say so. Honestly, I also miss the description first time. I only follow Stable version.
This is maybe caused, the new AppManager actually/absolutely need folder named "AppManager". Either in Internal storage or SDCard. AppManager not auto create the folder.
The Top description of Backup Volume setting say so. Honestly, I also miss the description first time. I only follow Stable version.
AppManager does not have any issues when using the "non work profile" version. It happens only with the work profile version. But I suspect this could be also related to "inferred mode: no root" in work profile mode.
I see.
I only use AppManager to manage backup. No experiences with Profiles.
Nevertheless, Issue title match with what I experience from fresh install of Stable v3.0.0 and the mentioned folder didn't exist (for whatever reasons). Creating the mentioned folder stop the message, aside all backups will go there.
This is maybe caused, the new AppManager actually/absolutely need folder named "AppManager". Either in Internal storage or SDCard. AppManager not auto create the folder.
Thanks for sharing this. It seems to be a different issue but an issue nonetheless.
Update: Actually, the issue reported by @MicroBeast appears to be exactly the issue. I've just tested it on my end. This will be fixed in the next patch release, but in the mean time, this issue could easily be fixed by creating AppManager folder in the root directory of the SD Card.