-
Notifications
You must be signed in to change notification settings - Fork 14
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
Unable to add BIG-IP after upgrade to VSCode 1.83 #230
Comments
Same here. I opened VSCode 1.83 today and all of my F5 Hosts were gone. I get the same message as @jgoldsworth-f5 when I try to create a new one. I uninstalled and reinstalled the F5 extension but it did not help. The runtime status of my F5 Extension is "Not yet activated." I am running Windows 10 Enterprise Version 10.0.19044 Build 19044. VSCode info: |
Same error for as for previews posts. |
dub of #229 |
I have the same error as well |
Thanks for opening this issue. Looking into this. For now, people seem to have success with rolling vscode back to 1.82 |
Downgrading VSCode to v1.82 resolved this issue for me (and also fixed issues I was having with Docker extension). |
confirmed as well under both stable and preview apps, going to roll stable back to 1.82. Also of note, after installing the extension, I right click on an unencrypted UCS file and it never loads in F5 config explorer. Been using this for years and first time I've run into this. Status of the extensions under both apps is not activated. |
Just released 3.15. that should fix this. Please confirm |
Works for me now, confirmed that this fixed my issue. Thank you! |
fix confirmed. closing |
After an ugrade to VSCode 1.83, I am no longer able to view or access any of my existing devices. Upon attempting to add a new device I'm getting the following error:
"Error running command f5.addHost: command 'f5.addHost' not found. This is likely caused by the extension that contributes f5.addHost."
I've attempted installing an older version of the extension with no luck. This issue occurs on both Windows and Mac OS. This is also occuring for other people as well that I am working with.
The text was updated successfully, but these errors were encountered: