Explorer does not refresh after switching profiles
See original GitHub issue- OS: Windows 10 (18362) running vscode/WSL (remote Ubuntu 18.04)
- VS Code version: 1.50.0-insider
- AWS Toolkit extension version: 1.15.0
Question
After changing profiles from the status bar “profile picker”, the AWS Explorer tree still shows contents from the previous profile, even after clicking “Refresh AWS Explorer”.
The expected behavior is that AWS Toolkit re-connects to AWS using the new profile, followed by a refresh of the Explorer.
My profiles are in ~/.aws/credentials and they use credential_process for SSO login.
Is this behavior by design?
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
File Explorer doesn't refresh automatically
1. Press Windows Key + R and type SYSDM.CPL in Run. Click OK or press Enter key. 2. In System Properties window, switch...
Read more >7 Ways to Fix File Explorer if It's Not Refreshing Automatically
What can I do if File Explorer does not refresh automatically? ; Click the Start button. · On the Windows update page, select...
Read more >Folders not refreshing automatically in Windows 10
Open Task Manager · In the Processes tab, right-click on the Windows Explorer process and click Restart cleanly restart explorer via task manager...
Read more >FIX: Explorer Does Not Refresh Changes in Windows 10/11.
How to FIX: Explorer No Refresh After Changing Files/Folders in Windows 10/11. ; Press CTRL + ; Open File Explorer and from the...
Read more >Desktop, Folder or Explorer does not refresh automatically
The Windows Desktop or Windows File Explorer window or folder will automatically refresh itself when you make a change to its contents. This ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

No, the refresh does not work in any context - here’s everything I tried so far:
rum-p), explorer is showing the correct tree/resourcesrum-dp: output log says"Credentials changed (profile:rum-dp), updating AWS Explorer"but explorer still shows old resourcesrum-dprum-dp), explorer still shows old resourcescredentials: found profiles: default,rum-dpp,rum-dp,rum-d,rum-t,rum-pwhich are all in my~/.aws/credentialsfile … I expected to see new resources after the restart!note: it would be helpful to see the AccountId in the output logs. At some point, i see
Getting AccountId from region us-west-2in the log -> after this line it would be great to see the AccountId …Not sure if you both gave my last comment thumbs up because you thought I got it working (?) - if so, that means my comment was not clear - i edited it to clarify that the refresh is still not working …
@bryceitoc9 - I have not tried the non-insider build yet but i will when i have some extra time and will report back here… thx!