Skip to content
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

Error: Invalid value for 'BACKUP_PATH' - is not readable #458

Open
JustBadCoder opened this issue Feb 5, 2024 · 3 comments
Open

Error: Invalid value for 'BACKUP_PATH' - is not readable #458

JustBadCoder opened this issue Feb 5, 2024 · 3 comments

Comments

@JustBadCoder
Copy link

Hi

I have reformatted my MacBook and installed MVT again, trying to scan an iOS backup.
However I get this error - is not readable

Error: Invalid value for 'BACKUP_PATH': Path '/Users/user1/Library/Application Support/MobileSync/Backup/00008130-000275E42213803A' is not readable.

The folder name is correct. If I remove the last "A", I get an error "does not exist" so I believe mvt-ios can read the folder.
But something else is wrong, any clues?

Did not have this issue before on the other Mac. Does mvt-ios need to be added to some macOS security settings etc?

Thanks

@roaree
Copy link
Contributor

roaree commented Feb 5, 2024

What version of macOS did you reformat to? I have the following permissions for iTerm under Security & Privacy > Files and Folders, and also for Full Disk Access. But I'm pretty sure I got a prompt to grant access very early on in usage.

image image

@JustBadCoder
Copy link
Author

I am on the latest macOS Sonoma.
I tried to give both terminal and mvt-ios full disk access through Settings, Security, without any results.
But I copied the whole backup folder to an external HDD.. And from here mvt-ios could read the folders fine.
So probably something with permissions yes, but I can copy them rather than jerk around to much in the OS... and thus prevent a new re-format MacBook Episode :D :D

@roaree
Copy link
Contributor

roaree commented Feb 6, 2024

Thanks for getting back. I'll leave this open until we can confirm if we need to add new instructions for Sonoma

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants