Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode: Wi-Fi details not showing up #254

Open
jelalanne opened this issue Sep 27, 2022 · 13 comments
Open

VSCode: Wi-Fi details not showing up #254

jelalanne opened this issue Sep 27, 2022 · 13 comments

Comments

@jelalanne
Copy link

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.

@jamesadevine
Copy link
Contributor

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

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

@jelalanne
Copy link
Author

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

@jamesadevine
Copy link
Contributor

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

@olegkhar
Copy link

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!

@jelalanne
Copy link
Author

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

@jelalanne
Copy link
Author

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

image

@olegkhar
Copy link

Thank you, @jelalanne , this helps.

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

@jelalanne
Copy link
Author

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

@olegkhar
Copy link

olegkhar commented Oct 3, 2022

@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!

@jelalanne
Copy link
Author

@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

@xisui-MSFT
Copy link

xisui-MSFT commented Oct 6, 2022

@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

@jelalanne
Copy link
Author

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?

@olegkhar
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants