mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5722] [bug]: Hoppscotch Desktop turns into white screen after some time #2232
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2232
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @GaoSSR on GitHub (Dec 24, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5722
Is there an existing issue for this?
Platform
Desktop App
Browser
Other (specify in additional info)
Operating System
macOS
Bug Description
What happened?
When I use Hoppscotch Desktop for a while, the entire app window suddenly turns into a completely white/blank screen.
There is no visible UI anymore (no sidebar, no tabs, no toolbar). The window stays white and the app becomes unusable until I close it and reopen Hoppscotch Desktop.
I do not see an error dialog, just the white screen.
@komapa commented on GitHub (Dec 24, 2025):
Same version of the app and happened to run into the same problem.
@GaoSSR commented on GitHub (Dec 24, 2025):
So this is indeed a bug, and I hope the developers can fix it as soon as possible because it greatly affects the user experience.
@CuriousCorrelation commented on GitHub (Dec 24, 2025):
Thanks for reporting this. There already is an tracking issue for this at #5716, please follow that issue for updates.
We've identified a potential cause for this which might have started in v25.11.0, where we changed how the store path is resolved.
A patch release will be issued for this soon.
In the meantime, you can downgrade to v25.10.1 to avoid the issue. See our downgrade guide for instructions on safely downgrading and restoring your data from automatic backups.
Previous releases are available at: releases repo.
Closing to keep discussion consolidated.