Renaming a shared file in Filr leaves behind the original file which cannot be deleted

In some situations, when a shared file is renamed in Filr by User-A it can result in two files in the Filr Desktop folder for User-B; one file with the new name which is fully accessible and a second file with the original name which is no longer accessible. The second file is local to User-B and does not appear in the Filr web interface or in the backend filesystem.

There are two scenarios in which this issue was reported:

Scenario 1:

1. User-1 shares a folder 'ACME-docs' with User-2 and grants Contributor rights
2. User-2 renames the file 'Shared with me\ACME-docs\Doc-draft.doc' to  'Shared with me\ACME-docs\Doc-final.doc'
3. User-1 notices that he now has two files under 'ACME-docs'
   a. Doc-draft.doc which can not be opened or deleted and also not synchronized with Filr server
   b. Doc-final.doc which is accessible and also synchronized with the Filr server

Scenario 2:

1. Under Public folder, User-1 makes the file 'Public\ACME-docs\Doc-draft.doc' Offline
   
2. User-1 renames the file 'Public\ACME-docs\Doc-draft.doc' to  'Public\ACME-docs\Doc-final.doc'
3. Since User-1 is not allowed to rename the file, a Permission Denied exception is displayed in the Filr Console's pending changes area with an Undo action button
   
4. User-1 clicks on Undo changes and notices that he now has two files under 'ACME-docs'
   a. Doc-final.doc which can not be opened or deleted and also not synchronized with Filr server
   b. Doc-draft.doc which is accessible and also synchronized with the Filr server

A fix for this issue is available in the Filr 3.3 Update.