cryptomator / cryptomator/cryptomator

Cryptomator + Microsoft Word in MacOS — adding empty folders and impossible to reopen a file without locking and unlocking vault

Open
#3,204 2 comments 0 reactions 0 assignees View on GitHub
mount:fuse os:mac
Dominant language
Java
Stars
16.1k
Forks
1.5k
Avg merge
2d 45m
Merged PRs (30d)
1

Description

### Please agree to the following

- [X] I have searched [existing issues](https://github.com/cryptomator/cryptomator/issues?q=) for duplicates
- [X] I agree to follow this project's [Code of Conduct](https://github.com/cryptomator/cryptomator/blob/develop/.github/CODE_OF_CONDUCT.md)

### Summary

When I save a file for the first time with Word in a Cryptomator Vault (saved in Onedrive), it adds empty folders that end in filename.docx.sb-xxxxxxxxx-xxxxxx (the x are letters and numbers). Once I close the file, I can’t open it again without locking the vault and unlocking it again.

### What software is involved?

- Operating System: macOS Sonoma 14.0
- Cryptomator: 1.11.0
- Microsoft Word (with Office 365): 16.78.3

### Volume Type

FUSE-T

### Steps to Reproduce

1. Create new file in Word
2. Save in Vault

That’s it, the empty folders appear.

When closing the file and trying to open it again, Word complains that it can’t open the file. When locking the vault, unlocking it and opening the file again, it can be opened.

When I save after doing that procedure or when I modify an existing document, new empty folders are not created.

### Expected Behavior

No empty folders.
Files can be opened and closed without locking and unlocking the vault.

### Actual Behavior

When I save a file for the first time with Word in a Cryptomator Vault (saved in Onedrive), it adds empty folders that end in filename.docx.sb-xxxxxxxxx-xxxxxx (the x are letters and numbers).
When I close the file, I can’t open it again without locking the vault and unlocking it again.

### Reproducibility

Always

### Relevant Log Output

_No response_

### Anything else?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.