starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #4983] [bug]: Could not fetch a valid release json from the remote #1892

New issue

Closed

opened 2026-03-16 22:17:10 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 22:17:10 +03:00

Owner

Originally created by @Gavinluo on GitHub (Apr 11, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4983

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Current behavior

When i open the hoppscotch-desktop.exe ，Screen displays "Could not fetch a valid release JSON from the remote" and then immediately exits. My computer cannot access external networks.
version:2025.3.1

Steps to reproduce

open the hoppscotch-desktop.exe

Logs and Screenshots

Environment

Release

Hoppscotch Version

Local

Interceptor

Native - Desktop App

Browsers Affected

No response

Operating System

None

Additional Information

No response

Originally created by @Gavinluo on GitHub (Apr 11, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4983 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior When i open the hoppscotch-desktop.exe ，Screen displays "Could not fetch a valid release JSON from the remote" and then immediately exits. My computer cannot access external networks. version:2025.3.1 ### Steps to reproduce open the hoppscotch-desktop.exe ### Logs and Screenshots ```shell ``` ### Environment Release ### Hoppscotch Version Local ### Interceptor Native - Desktop App ### Browsers Affected _No response_ ### Operating System None ### Additional Information _No response_

kerem

2026-03-16 22:17:10 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 22:17:27 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 11, 2025):

Hi @Gavinluo, the error message

Could not fetch a valid release JSON from the remote

is expected behavior when the application can't check for updates due to variety of reasons. This is simply indicating that the check for update procedure has failed, and the user might need to make sure the app is up to date by perhaps checking for new releases from the website.

This message should not cause the application to exit, the app should still launch successfully after displaying this message.

Here's a video demonstrating that, when a machine is completely offline (no WiFi or Ethernet connection), the message appears briefly but the application continues to launch normally.

https://github.com/user-attachments/assets/704b9896-16aa-4281-9a7b-68da397aca1d

What you're experiencing is likely an environment-specific issue rather than a problem with the Hoppscotch application itself. The app might be launching in a different Windows workspace, or there could be security software blocking the application. It's also possible that another application might be interfering with Hoppscotch's startup.

To troubleshoot, you can check Windows Task Manager to see if Hoppscotch is running but not visible. You might also want to temporarily disable any security software to test if it's blocking the application, or try running the application as an administrator.

@CuriousCorrelation commented on GitHub (Apr 11, 2025): Hi @Gavinluo, the error message > Could not fetch a valid release JSON from the remote is expected behavior when the application can't check for updates due to variety of reasons. This is simply indicating that the check for update procedure has failed, and the user might need to make sure the app is up to date by perhaps checking for new releases from the website. This message should not cause the application to exit, the app should still launch successfully after displaying this message. Here's a video demonstrating that, when a machine is completely offline (no WiFi or Ethernet connection), the message appears briefly but the application continues to launch normally. https://github.com/user-attachments/assets/704b9896-16aa-4281-9a7b-68da397aca1d What you're experiencing is likely an environment-specific issue rather than a problem with the Hoppscotch application itself. The app might be launching in a different Windows workspace, or there could be security software blocking the application. It's also possible that another application might be interfering with Hoppscotch's startup. To troubleshoot, you can check Windows Task Manager to see if Hoppscotch is running but not visible. You might also want to temporarily disable any security software to test if it's blocking the application, or try running the application as an administrator.

kerem commented

2026-03-16 22:17:32 +03:00

Author

Owner

@Gavinluo commented on GitHub (Apr 11, 2025):

Yes, you are right. I have tested it on another PC, and it show this error but worked. I have also checked the security software logs, and there is nothing related to Hoppscotch. Additionally, I have even upgraded WebView2 to version 135, but the error still exists. Sorry i cant record video for this error.

@Gavinluo commented on GitHub (Apr 11, 2025): Yes, you are right. I have tested it on another PC, and it show this error but worked. I have also checked the security software logs, and there is nothing related to Hoppscotch. Additionally, I have even upgraded WebView2 to version 135, but the error still exists. Sorry i cant record video for this error.

kerem commented

2026-03-16 22:17:37 +03:00

Author

Owner

@CuriousCorrelation commented on GitHub (Apr 11, 2025):

Hey @Gavinluo, thanks for confirmation!

I'm transferring this issue to our Discussions section under the Q&A category since we've established it's not actually a bug in the app itself, but rather something specific to your environment.

This will keep our issues tracker focused on actual bugs while ensuring your question remains visible to others who might encounter similar environment-specific problems.

I'm happy to continue helping with diagnostics in the discussion thread, and if anyone discovers a solution, it will be more easily found by others there.

@CuriousCorrelation commented on GitHub (Apr 11, 2025): Hey @Gavinluo, thanks for confirmation! I'm transferring this issue to our Discussions section under the Q&A category since we've established it's not actually a bug in the app itself, but rather something specific to your environment. This will keep our issues tracker focused on actual bugs while ensuring your question remains visible to others who might encounter similar environment-specific problems. I'm happy to continue helping with diagnostics in the discussion thread, and if anyone discovers a solution, it will be more easily found by others there.