What's new in OmniPresence 1.6
Jul 27, 2018
- Improves compatibility with macOS High Sierra. This release requires macOS 10.13.
New in OmniPresence 1.5.2 (Apr 12, 2017)
- Stability - Addressed a common crash that could occur when OmniPresence was running in the background.
New in OmniPresence 1.5.1 (Nov 10, 2016)
- Unsupported Synced Folder Locations — The user Library folder is now considered an unsupported folder location by OmniPresence.
- Error Messages — OmniPresence now provides more helpful error messages when sync fails in certain scenarios.
New in OmniPresence 1.5 (Oct 20, 2016)
- Unsupported Synced Folder Locations — In order to avoid potential data loss, OmniPresence 1.5 detects the location of synced folders and automatically disables sync for folders currently saved to unsupported locations. To re-enable syncing for these folders, open the OmniPresence menu and follow the prompts to move the synced folder to a supported location.
- Unsupported Synced Folder Locations — The user Desktop and Documents folders are now considered unsupported synced folder locations by OmniPresence as these folders can be synchronized via iCloud Drive on macOS Sierra.
- Unsupported Synced Folder Locations — The default synced folders created by Amazon Drive, Box Sync, Google Drive, OneDrive, and SpiderOak Hive are now considered unsupported synced folder locations by OmniPresence.
- Setup — The user home folder is now the default location for newly configured sync folders.
- Help — The in-app OmniPresence Help, which can be accessed via the sprocket in the OmniPresence menu, has been fully rewritten.
New in OmniPresence 1.4.1 (Dec 3, 2015)
- Crash — Avoid a crash when there are unexpected errors selecting a folder for the sync location.
New in OmniPresence 1.4 (May 14, 2015)
- Crash — Fixed a crash that could happen when launching OmniPresence by opening a omnipresence-config file.
- Crash — Fixed a potential crash when closing the About panel.
- Crash — Fixed a rare crash when doing a software update check.
- Crash — Fixed a crash when attempting to sync with a WebDAV server that doesn’t return ETag values.
- Setup — When performing WebDAV conformance checks, retry tests that fail due to timeout a few times. This should help configuring OmniPresence when the link to your server is slow.
- Setup — We no longer clear your previously entered credentials during setup if you opt to retry a failed conformance test (possibly due to timing out).
- Logging — Fixed repeated archiving of “Archived bookmark data was flagged as stale…” messages.
New in OmniPresence 1.4 R232834 Test (May 6, 2015)
- Crash — Fixed a crash that could happen when launching OmniPresence by opening a omnipresence-config file.
New in OmniPresence 1.4 R232546 Test (Apr 30, 2015)
- Crash — Fixed a potential crash when closing the About panel.
- Crash — Fixed a rare crash when doing a software update check.
- Crash — Fixed a crash when attempting to sync with a WebDAV server that doesn’t return ETag values.
- Setup — When performing WebDAV conformance checks, retry tests that fail due to timeout a few times. This should help configuring OmniPresence when the link to your server is slow.
- Setup — We no longer clear your previously entered credentials during setup if you opt to retry a failed conformance test (possibly due to timing out).
- Logging — Fixed repeated archiving of “Archived bookmark data was flagged as stale…” messages.
New in OmniPresence 1.3 R227365 (Feb 27, 2015)
- Error Handling — Fixed a data loss bug that could occur rarely if the sandboxing system starts denying access to portions of your synchronized folder.
- Error Handling — Fixed a problem where the menu item would sometimes not show an error indicator when one of the synchronized folders couldn’t be synchronized.
- Setup — OmniPresence will no longer let you put one synchronized folder inside another.
- Last Sync — The “Last Sync” date should no longer say “None” when launched.
- Performance — Improved use of previous redirects during WebDAV operations to avoid extra round trips with the server.
- Server Clean-Up — OmniPresence now cleans up old versions of files on the server in some cases it didn’t before.
New in OmniPresence 1.2 (Oct 30, 2014)
- New:
- Yosemite interface — Updated the app interface and the icons for synced folders to look more at home on Yosemite.
- Yosemite Dark Mode — Updated the menu bar icon to display properly when using Yosemite’s Dark Mode, and updated the main window’s appearance to be more usable in dark mode.
- Updated:
- Auto-Sync — Made auto-syncing happen more reliably when changes are synced to the same cloud location from another device on the same network.
- Fixed:
- Error Handling — If too many attempts are made to transfer a file, OmniPresence will now pause syncing and offer to report the error.
- Conflicts — OmniPresence no longer permanently renames files when there is a conflict. Instead, each client locally renames the files and doesn’t send those renames to the server (which could cause extra conflicts in heavy usage cases). If you rename one of the files that is in conflict, that file gets renamed on the server as well and other clients will see that name. If there is only one version of a file left in conflict (maybe you deleted the other conflicting versions or renamed them to something else), OmniPresence will rename it back to the original user-specified name.
- Spurious conflicts — Fixed an issue where OmniPresence would treat an interrupted network connection as a failure, and if it turns out the operation actually succeeded it would treat that as a conflict (since it didn’t think it made that change itself). This should make syncing much more reliable when syncing over slow (or distant) networks.
- Simultaneous setup — OmniPresence conformance tests will no longer fail when more than one device is performing those tests at the same time.
- Open at Login — Fixed some cases where the “Open at Login” menu item wouldn’t work properly.
- Crash — Fixed a crash that could happen when updating the settings for a cloud location.
New in OmniPresence 1.1 (Nov 13, 2013)
- Server Clean-Up: OmniPresence will now correctly clean up temporary files left on the server during previous syncs.
- App Icon: OmniPresence has a new application icon.
- Many Smaller Fixes and Improvements
New in OmniPresence 1.0.2 (Sep 19, 2013)
- Encryption — When OmniPresence is configured to use an encrypted https:// connection to a server, it will now ignore any location headers from that server that tell it to switch to unencrypted http://. Our assumption is that your configuration choice indicates that you want all sync operations to be encrypted, and that any servers which redirect to unencrypted http:// locations for these resources are simply misconfigured.
New in OmniPresence 1.0.1 (Sep 19, 2013)
- Hopefully Fixed Our Most Frequent Crash — OmniPresence has been remarkably stable, but we’ve seen a few reports of it crashing in the background when it tries to access the keychain to authenticate a sync operation with the server. We haven’t been able to reproduce this on demand, but we’re guessing that some of the operating system’s keychain code might not be thread-safe. We’ve rearranged our code to look up credentials from the main thread to see if that fixes the problem.
- Sync on Wake — OmniPresence will always try to sync when the computer wakes from sleep, not just when it’s prompted by a network state change.
- Conformance Tests — Improved OmniPresence’s server compatibility tests.
- Error Messages and Crash Reports — OmniPresence’s error messages now include more information so that our Support Humans can assist in troubleshoooting.
- Smaller Fixes and Improvements