x360Sync Version 2.7.1 - Known issues

Written By Tami Sutcliffe (Super Administrator)

Updated at August 23rd, 2021

Release notes for 2.7.1

Issue #1 Summary 

If the SyncedTool for Desktop does not have permission to write into a destination folder, no warning message is provided to the user.

Prerequisite for the issue to occur:

A folder is mapped using the File Server Enablement feature. 

When a user performs the following actions:

  1. Creates a new folder
  2. Changes the system permission of that folder to Read Only
  3. Maps a team share or user account to this folder using File Server Enablement

The following scenarios can occur:

  • SyncedTool for Desktop does not generate warnings.
  • The icon overlay continuously shows syncing in progress.

Workaround:

Confirm the SyncedTool service has both read and write access to the synced folder.

To diagnose this issue, please look for the following string in the SyncedTool logs:

ERRR|system|||Failed to sync initial metadata ... Access is denied: "[File Path]"

In a future release, we'll extend error handling to provide information about exceptions that block the sync process to the user interface.

-----------------------------------------------------------

Issue #2 Summary

A Windows Team Share folder can't be opened if the folder name contains a trailing period.

Prerequisites for the issue to occur

  • SyncedTool for Desktop is installed on the Windows OS.
  • The Team Share folder name contains a trailing period.

When a user performs the following actions:

  1. Creates a Team Share using the Web Portal and includes a trailing period in the folder name
  2. Registers a user on SyncedTool for Windows
  3. Waits until the Team Share folder is fully synchronized
  4. Tries to open a Team Share in the SyncedTool Folder on a user's desktop

The following scenario can occur:

A Location is unavailable message is displayed when a user attempts to open a Team Share folder with a trailing period in the folder name.

Workaround:

Avoid trailing periods in Team Share folder names.

-----------------------------------------------------------

Issue #3 Summary

If x360Sync is installed on a drive other than C, the Celery service fails to start  (Celery is a distributed task management system and when Celery cannot start, alerts and scheduled reports will not work.)

Prerequisites for the issue to occur:

  • Python is installed on C drive. (For example, Python may have been installed as part of a previous x360Sync Private Cloud Server installation.)
  • x360Sync Private Cloud Server is not installed. (For example, x360Sync Private Cloud Server may have been uninstalled.)

When a user performs the following actions:

  1. Runs the x360Sync Private Cloud Server installation
  2. Changes the location (when asked), from the C drive to any other available drive

The following scenario can occur:

The x360Sync Private Cloud Server installation is successful, but the Celery service cannot start.

Workaround:

Uninstall Python, and perform the x360Sync Private Cloud Server installation again. This will allow control over the Python installation location, during the x360Sync Private Cloud Server installation.

-----------------------------------------------------------

Issue #4 Summary

A large number of files can cause the uploading process to get stuck in the syncing state.

Prerequisite for the issue to occur:

SyncedTool for Desktop is installed on Windows OS.

When a user performs the following actions:

Copies more than ten thousand (10,000) files to the Synced Folder at once

The following scenario can occur:

In some cases, during the upload, the process gets stuck (regardless of the file size).

Workaround:

Use the Pause/Unpause option in the SyncedTool for Windows GUI, to allow the uploading process to continue.  Depending on the number of files involved, it is possible the uploading process will be interrupted in the same way again. In that case, repeat the use of the Pause/Unpause option until the upload is complete.

This rare issue was found during our stress testing and in future versions, we are planning to address this by improving SyncedTool for Desktop's resilience, especially the ability to self-recover.

-----------------------------------------------------------

Issue #5 Summary

An extra removed event is entered in the Windows event logs when a user resolves a collision, regardless of the method used to resolve the collision.

Prerequisites for the issue to occur:

  • SyncedTool for Desktop is installed on Windows OS.
  • There is a file with a collision.

When a user performs the following actions:

  1. Resolves a collision on a file using the Discard,Rename or Overwrite methods
  2. Checks the Windows event logs

The following scenarios can occur:

  • If the Discard method was used to resolve the collision, two removed events (for the same file) are logged in the Windows Event log.
  • If the Rename method was used to resolve the collision, one extra removed event is logged along with the rename events in the Windows Events log.
  • If the Overwrite method was used to resolve the collision, one extra removed event is logged along with the overwrite events in the Windows Events log.

-----------------------------------------------------------

Issue #6 Summary

[For macOS only] The Lock icon is not refreshing when a status is changed.

Prerequisite for the issue to occur:

SyncedTool for Desktop is installed on the macOS. 

When a user performs the following actions:

  1. Opens a synced folder in Finder
  2. Locks a file or a folder using the context menu or the Web portal

The following scenario can occur:

The lock icon will not appear until the macOS Finder window is refreshed manually.

Workaround:

The status in the Finder window can be refreshed by navigating away and then returning.

This issue will be addressed in the next version. 

-----------------------------------------------------------

Issue #7 Summary

[For iOS 4.8 and macOS 2.7.1 devices only]

Application functionality may be limited when the dark mode is enabled on iOS 4.8 and macOS 2.7.1 devices. (The file structure may not be visible in dark mode.)

Prerequisite for the issue to occur:
Dark mode is enabled on an iOS 4.8 or macOS 2.7.1 device. 

Workaround:
If app users experience issues with the file structure not being visible, please disable the dark mode.

Resolution plan: The dark mode limitations will be addressed in an upcoming release.

-----------------------------------------------------------

If you would like to learn more, we invite you to sign up for one-on-one training.

Please contact your Partner Success Manager or Support if you have any questions.

For a complete list of status updates and scheduled maintenance advisories, please bookmark or subscribe to the Status page.