Unable to unlock a Vault in File app on Apple Vision Pro

[justinLia]

Please agree to the following

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

Summary

Unable to unlock a Vault in File app on Apple Vision Pro

System Setup

• Vision OS: [1.1.2]
• Cryptomator: [2.5.2 (1228)]

Cloud Type

iCloud; Google Drives

Steps to Reproduce

1. Complete the vault setup
2. The Lock Now button is dark, and the status is locked.
3. Click to enter the Files app
4. The Files app shows that it is locked, and it seems that it cannot be unlocked using Optic ID, and it cannot pop up a small passport window to enter the password like the iPad version. When select the unlock button, it will open the Crytomator app.
5. In Cryptomator, we still cannot click the Lock Now button and there is no way to unlock.

Expected Behavior

It should unlock in the Files app by using Optic ID or passcode, just like it does on iPad and iPhone

Actual Behavior

The Files app shows that it is locked, and it seems that it cannot be unlocked using Optic ID, and it cannot pop up a small passport window to enter the password like the iPad version. Go to Cryptomator again, and still cannot click the Lock Now button(dark color).

Reproducibility

Always

Relevant Log Output

No response

Anything else?

No response

[tobihagemann]

Thank you for reporting this issue. Does visionOS 2 change anything? To be honest, we aren't able to test this since we don't have an Apple Vision Pro...

[justinLia]

Thank you for reporting this issue. Does visionOS 2 change anything? To be honest, we aren't able to test this since we don't have an Apple Vision Pro...

Thank you for your reply! I just tested it again, the issue still happen with visionOS 2. Are you able to use the simulator at Xcode or something else to test it? I am happy to provide more information that you need, Thanks!

[tobihagemann]

Yes, we tested it briefly in the Simulator and can confirm that it doesn't work there either. Just wanted to make sure if it's different on a real device.

We'll look into it further and document our findings.