While the x360Sync Thin Client is in Beta mode, our team is working actively to resolve several known issues as quickly as possible. 

Below is a full summary of the prerequisites for these issues to occur. 

Please see the Plans section for each issue below to understand how we intend to address it.

Contents [Updated 9.23.20] A file is cached when hovering over the file name or right-clicking on the file in certain circumstances When switching the Windows Explorer View settings to Large Icons, some content downloads The file size limit does not update until the agent service restarts When a collision occurs, a Location unavailable error occurs when attempting to access the Synced Folder in some cases, deleting an unpinned folder does not delete a local copy of the folder File status overlay switches to green checkmark after renaming a file but the sync process is not complete When the Manual Collision Resolution setting is turned on, duplicate collisions generate

---

Issue #1 Summary [9585] 

In certain instances, a file is cached when hovering the mouse cursor over the file name or right-clicking the file. 

Steps to reproduce 

1. Navigate to the Synced Folder. 
2. Hover over or right-click an unpinned file.

Expected result

• When hovering over a file name, a user sees file information.
• When right-clicking a file, the file context menu displays.
• The file remains unpinned.

Actual result

The file is cached.

Plan

With the Thin Client, we provide a virtual file system. The file system receives requests from various applications, such as Windows Explorer, Microsoft Word, or any other editors. It also manages the apps that crawl the file system without a user request, such as anti-virus programs or search indexing, and other applications.

Applications such as anti-viruses, search indexers, and others are accessing a file's content in the background. As part of the BETA release, we did not restrict applications from accessing the unpinned file's content As a result, a file's content might be cached without the user's intention. We plan to conduct deeper research to avoid unintentional downloads in future versions.

---

Issue #2 Summary [9605]

When switching the Windows Explorer View settings to Large Icons, some content downloads.

Steps to reproduce:

1. Navigate to Synced Folder using Windows Explorer.
2. Change the View settings to Large Icons.

Expected result

• A user can see the thumbnails of the cached and pinned files.
• The file remains unpinned.

Actual result

A file's content is downloaded without a user request.

Plan

Please refer to issue 1 above.

---

Issue #3 Summary [9607]

File size limit does not update until the agent service restarts.

Steps to reproduce

1. In the administrative Web Portal, set the organization file size limit to 10 MB.
2. Attempt to upload a 15 MB file through the Synced Folder.
3. Return to the Web Portal and set the organization file size limit to 20 MB.

Expected result

File uploads automatically without user intervention.

Actual result

File does not upload until a user manually pauses or restarts the Thin Client.

Plan

This issue will be resolved in a future version.

---

Issue #4 Summary [9566]

When a collision occurs, a user sees the Location unavailable error when attempting to access the Synced Folder.

Prerequisites

• Machine 1 has the desktop client installed.
• Machine 2 has the Thin Client installed.

Steps to reproduce

1. On Machine 1, open a .docx file (Microsoft Word).
2. On Machine 2, open the same file.
3. On Machine 2, pause the sync process.
4. On Machine 1, make multiple edits of the file and observe the changes syncing to the cloud.
5. On Machine 2, attempt to edit the file's content.
6. On Machine 2, close the Microsoft Word application.
7. On Machine 2, attempt to navigate to the Synced Folder using Windows Explorer.

Expected result

• Users can see a collision warning regarding the file’s edits.
• Users can access the Synced Folder content using Windows Explorer.

Actual result

Users cannot access Synced Folder content, and the Location unavailable error displays.

Plan

This issue will be addressed as part of the BETA release.

---

Issue #5 Summary [9778]

In some instances, deleting an unpinned folder does not delete a local copy of the folder.

Steps to reproduce:

1. Select an unpinned folder.
2. Attempt to delete the selected folder.

Expected result:

• All the files within the folder delete locally and in the cloud.
• All the files within the folder disappear from the Windows Explorer view.
• The folder disappears from the Windows Explorer view.
• The folder is deleted on the server, and a user cannot see it on the web portal unless Show Deleted  is turned on.

Actual result:

• All the files within the folder are deleted successfully.
• The folder structure remains locally and in the cloud.
• The Web Portal also shows that some of the delete events for that operation do not sync to the server.

Plan

This issue is planned to be fixed as part of the BETA release.

---

Issue #6 Summary [9696]

Summary

After renaming a file, the file status overlay switches to pinned (green checkmark) even though the sync process is not complete.

Steps to reproduce

1. Copy a file to Synced Folder.
2. Rename the file while the sync still is in progress.

Expected result

• The file is renamed locally and in the cloud.
• A user can see the file with the new name on the web portal.
• The file overlay indicates the Loadingstatus until fully synced.

Actual result

• The file is renamed locally and in the cloud.
• A user can see the file with the new name in the Web Portal.
• The file overlay icon indicates the Loading status until fully synced.

---

Issue #7 Summary [9765]

Duplicate collisions generate when the Manual Collision Resolution setting is on.

Prerequisites

Two machines with the Thin Client installed and registered, with user accounts which have access to the same Team Shares.

Steps to reproduce

1. Turn off auto-locking and turn on Manual Collision Resolution.
2. Open a file on Machine 1.
3. Open the same file on Machine 2.
4. Create a new file revision on Machine 1 and confirm the changes are synced to the cloud.
5. Create second revision on Machine 1 and confirm the changes are synced to the cloud.
6. Create a new file revision on Machine 2.
7. Close the file on Machine 1.
8. Close the file on Machine 2. 

Expected result

A collision warning displays on the User Interface (UI) of Machine 2.

Actual result

• During the last step, the Thin Client creates a duplicate warning for the same collision (and the virtual driver might crash).
• A user can resolve both collision warnings.
• The Thin Client on Machine 1 shows the Loading icon overlay on the tray icon while attempting to sync the second collision file.
• If a user tries to open the second collision file on Machine 2, the file locks an application. 

 

---

Resolved Issues

• After editing a Microsoft Word document, a user sometimes cannot save it. [9746] Fixed in build 3.0.0.148
• In certain environments, files do not sync after a user re-registers a Thin Client. [9693] Fixed in build 3.0.0.148
• Collisions do not resolve automatically. [9725] Fixed in build 3.0.0.148

 

[ED-499]