BUG: Synology Drive Compatibility Issue

Issue: Substage returns "No such file or directory" errors when attempting to process files located in Synology Drive folders, despite having full disk access permissions.

Environment:

• macOS (on MacBook Pro/Mac Studio)

• Synology Drive client with local sync

• Files located at: /Users/richardjacobs/SynologyDrive

Behavior:

• Substage works perfectly with regular files on the local filesystem

• When attempting to process files in Synology Drive folders, receives path resolution errors

• Giving Substage full disk access does not resolve the issue

• Pausing Synology Drive sync does not fix the problem

Technical Context: Synology Drive appears to implement a virtual filesystem layer with extended attributes (@) on directories and files. This likely causes path resolution issues when Substage attempts to access these files directly.

Possible Root Causes:

1. Synology Drive's custom filesystem implementation uses redirection or virtualization that Substage's file access methods can't resolve

2. Extended attributes on Synology Drive files interfere with Substage's path resolution

3. Substage might be accessing files in a way that bypasses macOS's translation layer for these special directories

Request: Please consider adding support for properly resolving paths within Synology Drive's filesystem implementation. Many users rely on both Synology for storage and tools like Substage for productivity.

Thank you for your excellent app otherwise!