v2.2.2
Latest TBDNew: Diagnostic Logging
When something goes wrong with a connection, you can now turn on detailed logging and send the resulting file when reporting an issue. Logging is off by default in release builds, and the log writes to the shared app group container so it survives between launches.
- Toggle on under Advanced → Diagnostics on macOS, or Settings → Troubleshooting → Diagnostics on iOS
- Off by default in release builds, so there’s no overhead until you turn it on
Improvements
- Clearer SMB error messages: connection and browse failures now explain what actually went wrong instead of showing a generic “The operation couldn’t be completed” alert. Wrong credentials, missing shares, permission denials, and unsupported protocol versions each get a specific message, and a server that only speaks SMB1 (such as legacy Samba) now says so instead of being misreported as a bad password. Lower-level network failures (connection refused, host unreachable, DNS, TLS) are reported honestly too.
- Automatic log rotation: the current log rolls over once it passes your size limit (default 10 MB), and older copies are dropped past the keep count (default 4 files), so logs never grow unbounded.
- View logs without leaving the app: Show Logs in Finder on macOS opens the logs folder, and Share Logs on iOS exports the current log and any rotations via the system share sheet.
- Less intrusive review prompt: the App Store review request now appears only after you’ve actually used the app, waiting for a first-use grace period, a few successful transfers, and a polite interval before asking again.
Bug Fixes
- Fixed SMB shares on macOS getting permanently stuck after a brief network problem. A single failed directory listing (a timeout, dropped connection, or a server briefly unreachable after sleep or a network change) used to disconnect the share in Finder with no retry. Transient failures no longer disconnect the share, and any share left stuck by an earlier version reconnects the next time you open Driio.