syncthing-macos: macOS Ventura 13.0 sync fails due to com.apple.provenance metadata
update: This should be fixed once v1.22.2 is released, scroll down for details…
Since upgrading one of my Macs to Ventura 13.0, my folder will no longer sync (getting stuck on a piece of undocumented metadata called com.apple.provenance
I have tried removing the xattr with sudo xattr -d com.apple.provenance /path/to/file
but that isn’t working either.
Google has nothing about this really… anyone else running into this? Using syncthing-macos 1.22.0-1
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 18 (11 by maintainers)
Commits related to this issue
- Update README.md Add FAQ note about syncing xattrs from macOS 13.0 to macOS < 13.0. See issue #185. — committed to syncthing/syncthing-macos by xor-gate 2 years ago
Syncthing macOS is now shipping with release v1.22.2 (see commit https://github.com/syncthing/syncthing-macos/commit/bf62e121108d188e68d346ceb92c150630b0808b). Only the auto-updater is broken for some unknown reason, you can wait or download the signed/secure DMG.
Compiled a build this morning based on v1.22.2-rc.2 and this is now 100% fixed for me 👍
Note from @luckman212 (here https://github.com/syncthing/syncthing-macos/issues/154#issuecomment-1307221618) copied over here for convience:
Just adding this note here related to debugging going on over at https://forum.syncthing.net/t/com-apple-provenance/19262/17
For anyone who wants to increase the logfile size using the macOS bundle, you can use:
And when you’re done debugging, use this to revert things back to default:
I believe you need to fully quit the Syncthing app after each of these changes (not just stop/start the service) for it to take effect.
Thanks @luckman212 !
The README.md has been updated with appropiate information. Manual editing is the only way for now. See commit https://github.com/syncthing/syncthing-macos/commit/7fa1d1a0daa234638f0a3241f833da76677c8231
As noted on the forum, this can be disabled by configuration, unfortunately only by hand editing the config at the moment:
We might want to look into some sort of default black list per operating system perhaps, in the future.