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 Plan section for each issue below to understand how we intend to address it.
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
- Navigate to the Synced Folder.
- 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:
- Navigate to Synced Folder using Windows Explorer.
- 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
- In the administrative Web Portal, set the organization file size limit to 10 MB.
- Attempt to upload a 15 MB file through the Synced Folder.
- 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 [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
- Copy a file to Synced Folder.
- 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 #5 Summary [9992]
Summary
*.laccdb files are getting synced to the server.
Steps to reproduce
- Create a file with .laccdb extension.
- Copy and paste it in the Synced Folder.
Expected result
File does not get synced to the server.
Actual result
File is synced to the server.
Plan
The current plan is to address this issue as part of the BETA program.
Issue #6 Summary [AD-9949]
Summary
Windows search doesn't display cloud files in the search results.
The issue appears intermittently.
Steps to reproduce
- Using the Windows Explorer navigate to the Synced Folder.
- Type in the search box text matching any file name in the current folder.
Expected result
Files and folders with names matching the search string are displayed in the search results.
Actual result
Files and folders that have not been cached are not displayed in the search results.
Plan
The current plan is to address this issue as part of the BETA program.
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
- When a collision occurs, a user sees the Location unavailable error when attempting to access the Synced Folder. [9566]
- In some instances, deleting an unpinned folder does not delete a local copy of the folder. [9778]
- Duplicate collisions generate when the Manual Collision Resolution setting is on. [9765]
Comments
1 comment
Updated 12.1.20
Article is closed for comments.