mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #5653] [bug]: Unable to load Desktop client on MAC M1 15.7.2 #2189
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#2189
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 @batkite on GitHub (Dec 3, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5653
Originally assigned to: @CuriousCorrelation on GitHub.
Is there an existing issue for this?
Platform
Desktop App
Browser
Firefox
Operating System
macOS
Bug Description
Hi,
When I try to open the Desktop App on my Laptop it does not load the interface.
It was working fine until the last time I updated.
I see a window in the background that diseapears quickly then the blank screen above.
I'm running Mac OS Sequoia 15.7.2 on M1 Pro.
I've tried both ARM and Intel versions.
I've made sure no window is hidden somewhere.
Does not change if I change the default web browser.
In task manager I see this taking 100% all the time. and I have the same behavior after a reboot.
Happy to provide any logs I can.
Deployment Type
Self-hosted (on-prem deployment)
Version
25.11.0 (25.11.0)
@CuriousCorrelation commented on GitHub (Dec 4, 2025):
Hi @batkite, thanks for the report. Could you check what the logs are saying at
C:\Users\<username>\AppData\Local\io.hoppscotch.desktop\logs\io.hoppscotch.desktop.log~/Library/Logs/io.hoppscotch.desktop/io.hoppscotch.desktop.log~/.local/share/io.hoppscotch.desktop/logs/io.hoppscotch.desktop.logThey should look something like these:
We are looking for some obvious error logs or anything that might point to failure to load bundles.
NOTE: These may contain sensitive information so do verify and obfuscate such instances before posting those here.
@batkite commented on GitHub (Dec 4, 2025):
Hello @CuriousCorrelation ,
Only 2 "ERRORS" in the log that I could find :
From what I see after that :
it enters into this loop appearing again and again in the logs :
FYI : I removed the folder "Library/Application Support/io.hoppscotch.desktop", reinstalled the app and it launched. Obviously I lost all conf but the main issue is that I've exported my collection some time before and the file was over 50Mb which is not allowed to be re-imported back into the software due to the size limit.
@CuriousCorrelation commented on GitHub (Dec 4, 2025):
Thanks for the detailed logs @batkite. The backend is actually working correctly here, all assets are being served successfully. The loop is expected since that happens for all the ~200 asset files, you may see small differences between each if you were to
diffthose.The issue might be in one of the application state files that the frontend reads on startup or something to do with webkit itself.
When you "removed" the folder, did you move it to Trash? If you can recover
io.hoppscotch.desktop, could you share the contents of these files:hopp.store.jsonlatest/instance/hoppscotch-unified.storelatest/store/hoppscotch.hoppscotch.storeregistry.jsonThis would help identify exactly what caused the issue. As a bonus, recovering this folder would also restore your 50MB collection since it's stored in those
.storefiles, so you wouldn't need to re-import it.@batkite commented on GitHub (Dec 4, 2025):
Unfortunalty I cleared the trash.
It is not the first time I run into this issue so I will update this issue if I ran into it again.
@CuriousCorrelation commented on GitHub (Dec 5, 2025):
No worries, thanks for checking.
And yes if it happens again, I'd be happy to debug this further. We haven't seen this before, but since you mentioned it's happened more than once, tracking down the root cause would help us fix some root cause that might pop-up on different systems in the future.
Closing for now, but feel free to either reopen this issue or create a new one with those file contents.
@batkite commented on GitHub (Dec 9, 2025):
Hello @CuriousCorrelation ,
I do not have the permission to reopen the issue but today it happened again, I'm getting the blank screen.
Find the content you've requested :
hopp.store.json --> Could not find it
latest/instance/hoppscotch-unified.store
latest/store/hoppscotch.hoppscotch.store. --> This is a 12MB file so I cannot copy the content here.
registry.json
And actually, during the time I redacted this post, it actually opened...
That remind me that when I import my back-upped collection, it takes more than 7/8 minutes for it to be completed with the soft beeing irresponsive.
So it actually opens but seems not happy with the content of my collections being too big.
@CuriousCorrelation commented on GitHub (Dec 9, 2025):
Hi @batkite, thanks for the follow-up!
It seems that the app is loading correctly, but it's getting blocked while processing your large collection data on startup. The 12MB store file looks to be the culprit since we do hydrate collections/tabs or basically any persistence data upon first launch.
So the desktop backend is working fine (assets are being served successfully), but the frontend is locking up while parsing/hydrating that large dataset. This is actually a web app layer issue rather than something desktop-specific.
This is tangentially related to an existing known issue with large collection performance (#3233).
Could you open a new issue specifically for the startup/hydration blocking behavior with your findings? A good title would be
[bug]: App appears unresponsive after launch with large collections, just to help us track this case separately from the general collection slowness, since the symptoms and fixes are a bit different.And thanks for your patience!