Unlock vaults with same name not working on macOS using FUSE-T

[tobihagemann]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Unlock vaults with same name vault not working.

What software is involved?

• Operating System: macOS
• Cryptomator: 1.11.1
• FUSE-T: 1.0.34

Volume Type

FUSE-T

Steps to Reproduce

1. Create two vaults with same name
2. Unlock first vault
3. Unlock second vault

Expected Behavior

Two virtual drives exists, showing the contents of the first and second vault.

Actual Behavior

Only one virtual drive exists, showing the contents of the second vault.

Reproducibility

Always

Relevant Log Output

No response

Anything else?

This issue is very similar to #3114 #3344.

But with FUSE-T on macOS, there is no error. And it can be very confusing, which contents from which vault the virtual drive is actually showing.

[JaniruTEC]

IIRC this is also an issue with macfuse

[tobihagemann]

That's the thing, we fixed it in the macFUSE provider a while ago. I'm confused why we didn't fix it in the other providers.

[infeo]

See #3344 (comment).

Since we act towards the same case in the mount API, this issue also needs to be rescheduled.