Issue

Even though a folder invited via API [can_view_path] was moved to the trash, the following status persists.

• Although the down folder was deleted from the folder structure Top > Parent > down, Top > Parent remains displayed.

• When the down folder is opened, no contents are displayed.

Root Cause

When a folder invited via Share is moved to the trash for deletion, collaboration remains intact. This is to ensure the folder can be restored from the trash with collaboration settings preserved when necessary. Similarly, when a folder is invited via [can_view_path], the [can_view_path] settings remain active even after the folder is moved to the trash, and the path of the parent folder remains displayed.

The folder itself is inaccessible since it is in the trash, and its contents are not displayed.

Resolution

To prevent the parent folder path of the deleted folder from being displayed, restore the deleted folder from the trash first, remove collaboration from the folder, and then move it back to the trash.

Alternatively, when deleting a folder invited via [can_view_path], remove the collaboration first and then move the folder to the trash.