Folder 'obsidian' has an issue: unknown error

[Sparticuz]

I've been using synctrain pretty successfully, but have recently started receiving this 'unknown error' issue. When I open the obsidian folder, it states 'Unknown state: folder path missing'. I'm not sure how SyncTrain lost the path to the folder, but Obsidian still has everything in it. Is there a way to re-add the folder path or do I need to re-add the entire folder.

[pixelspark]

Hm it would help to know the exact underlying error. Could you generate a support bundle and send it over?

[Sparticuz]

Synctrain_support_bundle_647E38A7_0E51_4073_B2E6_581092A5F79F_7260.zip

[pixelspark]

The logs show this message:

Could not obtain file protection status for url /private/var/mobile/Containers/Data/Application/7CC8896B-C097-•••/Documents/Vault: Error Domain=NSCocoaErrorDomain Code=260 "The file “Vault” couldn’t be opened because there is no such file." UserInfo={NSURL=file:///private/var/mobile/Containers/Data/Application/7CC8896B-C097-•••/Documents/Vault/, NSFilePath=/private/var/mobile/Containers/Data/Application/7CC8896B-C097-•••/Documents/Vault, NSUnderlyingError=0x119aadad0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}} 

Most likely, the folder has moved behind the scenes for some reason. To resolve this, you can unlink the folder and re-add it. In some cases, you can also instruct Synctrain to relink the folder. To do this, go to the folder’s settings page. Look for the "External folder" option (or the error message, if applicable). Press and hold the option for a few seconds. A screen should appear where you can reselect the Vault folder. If the screen doesn’t appear, you’ll need to manually unlink and re-add the folder.

[pixelspark]

I have observed the same issue on my own device with an external folder, not sure why but for some reason something has moved. The fix is indeed to relink the folder using the long-tap method (on 'external folder' in folder settings) described above.

Please confirm that works for you as well. I will make the fix more obvious in the next version.