azure-sphere-samples icon indicating copy to clipboard operation
azure-sphere-samples copied to clipboard

VSCode: Wi-Fi details not showing up

Open jelalanne opened this issue 3 years ago • 13 comments

Hello,

Not sure if it's the right place to publish that bug, but didn't find a better suit. When running the Azure Sphere Explorer for the first time, with a connected device and after claiming it with the tenant, I am trying to connect it over the network, but when listing the available networks, only the infos names' appears, like on the next capture. Sorry it is in French, but i think the terms are quite obvious.

image

I suppose this is a bug. Hope you might do something about it.

jelalanne avatar Sep 27 '22 05:09 jelalanne

Hi @jelalanne! I suppose this is as good a place than any :smile:

I assume the bug is that the extension is listing "SSID" multiple times and each contains the same network SSIDs?

jamesadevine avatar Sep 27 '22 07:09 jamesadevine

Hi @jamesadevine, the thing is, they are not listed at all ^^' A lot of infos are missing, and for the wi-fi subject, only key words are shown, not the actual values

jelalanne avatar Sep 27 '22 09:09 jelalanne

Great, thanks for the additional details @jelalanne! A bug has been raised internally.

jamesadevine avatar Sep 27 '22 10:09 jamesadevine

Hi @jelalanne ,

Can you please turn on logging of CLI commands in the Output Window of Visual Studio? To do so, set the environment variable "AzureSphere.PrintCliCommands" to "1"; then restart Visual Studio and re-open the Azure Sphere Explorer.

There's probably going to be a lot of output, but you can clear the output window, and then reload the Available Networks node in the Explorer, and you'll see the output of the command azsphere device wifi scan -o json.

That may help us understand the problem better. Thank you!

olegkhar avatar Sep 27 '22 20:09 olegkhar

Hi @olegkhar, I'm actually using vscode. Is there any other equivalent of your suggestions?

jelalanne avatar Sep 28 '22 06:09 jelalanne

This is what I got from Azure Sphere - UI output when refreshing details of device, does this help?

image

jelalanne avatar Sep 28 '22 06:09 jelalanne

Thank you, @jelalanne , this helps.

Can you please tell me if any of the network names have non-ASCII characters in them?

olegkhar avatar Sep 28 '22 22:09 olegkhar

@olegkhar no, they are all either letters, numbers, dashes, underscores and spaces

jelalanne avatar Sep 29 '22 06:09 jelalanne

@jelalanne We identified the issue with the translation of our extensions and are working on correcting the translation. In the meanwhile, can you please try changing the language to English to see if the issue still reproduces?

Thank you!

olegkhar avatar Oct 03 '22 23:10 olegkhar

@olegkhar my VScode is currently already in english. I don't know why the extension is showing up french. And I don't know how to change extension's language specific setting

jelalanne avatar Oct 06 '22 08:10 jelalanne

@olegkhar my VScode is currently already in english. I don't know why the extension is showing up french. And I don't know how to change extension's language specific setting

There is no extension specific language setting. Displayed language is controlled by VS Code.

And I can't repro this behavior here. So my suggestion is to try to correct this with some usual approaches, for example:

  • Switch to French and then switch back
  • Run VS Code command "Clear display language preference"
  • Restart computer
  • Start VS Code from terminal using command like code . --locale=en
  • Reinstall VS Code

If none of these fix this problem, you'll need to open an issue for VS Code: https://github.com/microsoft/vscode

xisui-MSFT avatar Oct 06 '22 20:10 xisui-MSFT

Hello @xisui-MSFT , switch back and forth to french worked :) Thanks! I suppose this issue shall stay opened for you to repair the translation bug, or do I close it?

jelalanne avatar Oct 07 '22 07:10 jelalanne

Hi @jelalanne Thank you for confirming, and I'm happy to hear that you got the Extension working.

We'd like to keep this issue for a bit while we're fixing the Translation bug -- and we'll reply once we publish the Extension with the fix.

olegkhar avatar Oct 10 '22 22:10 olegkhar