Does not recognize Manifest.mbdb from old IOS backups (2014-2015)

[FTL1]

Hi, thanks for the great tool, I just need to figure out how to use it :-)

It seems this does not accept the Manifest.mbdb file. I tried changing the file extension but that doesn't help. Also, the cargo executable doesn't work (for me).

Any help/insight would be greatly appreciated! :-)

What I did:
I installed rustup via brew;

Then I followed your install instructions:

Build Locally

To build this locally, a nightly toolchain is required. You can install it using rustup:

rustup toolchain install nightly
Then, you can build the executable:

cargo +nightly build --release_

That last step (cargo ~) does not work. It throws this error:

_PS /Users/Nunyabiz/workspace/iosarchive> cargo +nightly build --release
error: no such command: +nightly

Cargo does not handle `+toolchain` directives.
Did you mean to invoke `cargo` through `rustup` instead?_

Then, I realized you said "For Mac users, you can download the pre-built binaries directly from releases page.", So I downloaded the binary into the local directory and ran this:

"local_iMac:~/workspace/iosarchive $ sudo ./ibackupextractor -l ~/Library/Application Support/MobileSync/Backup/bc5e093456f0a03b79551f5487ba063"

Got this output:

error: failed to open the manifest database

Caused by:
file not exists: "/Users/Nunyabiz/Library/Application Support/MobileSync/Backup/bc5e093456f0a03b79551f5487ba063/Manifest.db"

The backup directory has this in it:

Manifest.mbdb
Manifest.plist
Info.plist
Status.plist
<and LOTS of backup archives, named with typical hex-strings>

This was on a 2017 iMac28 running Ventura (13.7.1) on a i7-7700 with 64GB RAM.

[FTL1]

Note to others using macos (at least the Ventura version), when you copy dir paths and paste them into your shell ... they do not past the back\ slash to break the between "/Application Support/" (needs to be "/Application\ Support/"

I say this because it's easy to forget and when I attempt to show this in my issue up there^ the forward-slash gets rendered by github as a pipe "|" for some reason.

[unixzii]

The tool currently cannot parse Manifest.mbdb file, since it's a very old format and I don't have the environment to test it.