search

thomasnordquist / MQTT-Explorer

An all-round MQTT client that provides a structured topic overview
https://mqtt-explorer.com
Other
3.09k stars 291 forks source link

Cannot save broker connection (& "{}" white-on-red error on startup) #749

Closed jgbreezer closed 5 months ago

jgbreezer commented 10 months ago

At every start of the application after running the installable version, there is a white-on-red '{}' overlaid in a box at the bottom left (curved corners). This looks like an error message but there is no message just the empty curly brackets.

I can click to create a connection just fine though. Clicking 'save' button for any entered MQTT connection (and any future start attempts) after a fresh install fails. I can click connect instead and it connects and is usable.

Having seen another issue with a user with a similar problem, I'll note: The install process does not complain or ask for permissions of any kind, and it installs the executable into "C:\Users\MYUSER\AppData\Local\Programs\MQTT-Explorer\MQTT Explorer.exe" (no files created in Program Files or Program Files (x86)). I don't see any record of it in the AppData\Roaming folder. I haven't restarted or logged out in quite a while so will try that to see if it helps, but its not mentioned anywhere and nowadays isn't required for most apps. I do have multiple users on this machine.

If there's a debug flag or parameter or setting I can use to see more info/logging, happy to try that; or a debug build of it (am an experienced software developer, just on Linux generally not Windows)

jgbreezer commented 10 months ago

When I try to save a connection, I get the same '{}' error in white text on red background box at the bottom left of the window.

jgbreezer commented 10 months ago

PS I'm on Windows 11 Pro, version 22H2; system is up to date.

bj00rn commented 5 months ago

@jgbreezer you can build it on your own if you have node installed

  1. Clone repo

  2. Install dependencies and run

yarn install
yarn dev
jgbreezer commented 5 months ago

Thank you for your help. Figured it out, it was indeed a file permissions issue. Took ages to find though as I thought I'd set them right and it was actually in a higher level directory. Having an error message from the write failure about permission fail would have helped figure that out, instead of just "{}".

bj00rn commented 5 months ago

@jgbreezer can you provide a reproducible example?