Acknowledged

Simulator: Settings not available, Error 500

In the last weeks I've been having issues with the settings editor in the simulator. 
When I try to open the settings, it shows me: 

Settings not available
Unable to contact server.

Error code: 500

Usually when open it a couple of times it started to work again. I had to delete the bin directory and remove the GARMIN folder in the com.garmin.connectiq folder (removing the simulator files). But this morning that doesn't work anymore and I keep getting this error.


I reinstalled the SDK, tried on two different computers (one MacOS and windows), but the same issue there.
It doesn't seem to matter if I'm using language files or if I have 100 settings or 1, it keeps showing this error. Once uploaded to the IQ store, the settings work fine, just not in the SIM.

Opening the "Http Traffic Logs" seems to point at cloudflare and /valyrian/appSettings2/sdk/ returning the 500 error. Nothing useful in the logs as far as I can tell.

GreenBlack

  • Mine started working again, so I assumed whatever HTTP error was occuring had been resolved. Odd that it needs a non-local file to simulate any settings.

  • in reply to flocsy🤠

    You mentioned 2 days ago retrying worked for you.  I found the same a few days ago but now retry doesn't work.  Has retry also stopped working for you?

  • What the simulator is really doing under SDK 8.3.0

    When you click:

    Simulator → Application → Settings

    It loads something like:

    connectiq.garmin.com/.../index.html

    Inside an embedded Chromium WebView.

    That page then loads:

    • JavaScript bundles

    • UI definitions

    • Garmin settings components

    • Translation files

    • App metadata

    If any of those requests fail, Garmin’s webview throws a silent fatal error → the simulator reports “Error 500” even though your local server is fine.

    Fire So if all apps fail on SDK 8.3.0, then one of these is happening:

    1️⃣ A VPN that blocks Garmin's CDN

    Common with work VPNs, corporate VPNs, and Nord/Express/Proton.

    2️⃣ A proxy that cannot handle the embedded WebView's TLS

    If Windows LAN proxy settings are enabled → this breaks the editor.

    3️⃣ A firewall rule blocking embedded webviews

    Bitdefender, Kaspersky, ESET, and some corporate policies do this.

    4️⃣ DNS filtering (Pi-hole, AdGuard DNS, NextDNS)

    These can block the CDN or the iframe.

    5️⃣ A corporate machine policy blocking 127.0.0.1+remote web access combination

    Especially if your laptop is domain-managed.

    6️⃣ Garmin’s server unreachable in your region (rare)

    I have looked at all these in great details and hence I can only conclude that it is the last of these, the Garmin server is unreachable.