Skip to content

fix(files): blank screen when navigating mid-load #2501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lidel merged 1 commit into from
Jul 29, 2026
+13 −1
Merged

fix(files): blank screen when navigating mid-load #2501

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion src/bundles/files/actions.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -191,8 +191,20 @@ const actions = () => ({
const isConnected = store.selectIpfsConnected()
const isFetching = store.selectFilesIsFetching()
const info = store.selectFilesPathInfo()
if (isReady && isConnected && !isFetching && info) {
if (!isReady || !isConnected || !info || isFetching) return

try {
await store.doFetch(info)
} finally {
// Navigating away while a listing is in flight makes that navigation's own
// doFilesFetch() a no-op, because of the isFetching check above, and
// nothing else retries it. Without this the view keeps waiting on content
// for a path we already left. Runs on failure too, since a rejected fetch
// leaves the new path just as unfetched.
const current = store.selectFilesPathInfo()
if (current && current.path !== info.path) {
await store.doFilesFetch()
}
}
},

Expand Down
Loading