Bug: Opening a folder with an inaccessible shared folder inside breaks current tab

[TheKoTech]

Description

What happens is the contents of all folders stop showing. The app says there's nothing in them

Steps To Reproduce

1. Create a shared folder
2. Add a shortcut to it on a different device
3. Disconnect the device that shares the folder
4. Try to open the folder that contains the shared folder with Files
5. Now the folder renders empty, even though there is an inaccessible shared folder inside it. Any other files in the folder or even other folders in that tab will also stop showing any contents for up to a minute or two.

Expected behavior

Files should recognize that I stopped trying to see the shared folder's contents. It should also at least show the shared folder inside a folder, even if it's inaccessible.

Files Version

2.3.0.0

Windows Version

Windows 10 19043.1766

Relevant Assets/Logs

[Josh65-2201]

You will need to upload the logs files directly to github. You can get them in files settings > about > open log folder.

[TheKoTech]

debug.log
debug_fulltrust.log

[yaira2]

@Josh65-2201 @TheKoTech can you repro this in v2.5.20?

[TheKoTech]

@yaira2, yes, I reproduced it again. A little more on its behavior:

Sometimes I'm able to open the folder, containing the inaccessible shared folder. In these cases lots of 1-5 errors appear in the logs, after which the contents of the folder are rendered, except for the inaccessible folder.

Sometimes nothing happens. I waited for 5 min (measured) and nothing was logged, nothing changed in the UI.

---

Windows version: 10, 22H2, "Windows 10 Домашняя для одного языка" (Home for one language, Russian)
Build: 10.0.19045.3208

Files version: 2.5.20.0

debug.log

[yaira2]

Thank you for the update