Error Opening Repository after Updating to v0.13.0

[elevatorz89]

After updating to v0.13.0 from v0.13.0-rc1, Kopia throws the following error while trying to connect to the repository.

Connect Error: INTERNAL: internal server error: connect error: error opening repository: error connecting: unable to create shared content manager: error loading indexes: error downloading indexes: error loading index blob xn15_f._022f18e6d28f59eb4bf1789720d1b75-s41669725541c852e11c-c1: decrypt blob: unable to get index blob IV: invalid blob ID: xn15_f._022f18e6d28f59eb4bf1789720d1b75

Before rebooting my machine, I had issues with backing up. Unfortunately, I did not get a snippet of this other error.

[patrsc]

I have the same issue with an external hard drive (formatted with ExFAT) being used as repository location on macOS. In my case the problem is that macOS creates files starting with ._ on external drives to store filesystem metadata (see also Why are dot underscore ._ files created, and how can I avoid them?). After running the command

dot_clean /path/to/kopia-repository

I was able to connect to the repository again. However, this solution is not permanent, because macOS will create these files on subsequent write operations to the repository. Is it possible that Kopia ignores these files by default?

[mrtorrent]

I just ran into this issue on KopiaUI 0.15.0 I also have an external drive formatted ExFAT. I was pulling my hair out trying to figure out how to get Kopia to connect to my repository after it was created. Thanks to ChrisA on the forum and @patrsc, now I know what the problem is and how to work around it, but as @patrsc points out, it will keep happening when macOS recreates the files. Can't Kopia recognize these files and handle them gracefully?