aws-extend-switch-roles icon indicating copy to clipboard operation
aws-extend-switch-roles copied to clipboard

Blank list on version AWS extensuon 6.0 and chrome version 137.0.7151.57

Open jorgemartineztala opened this issue 6 months ago • 1 comments

Describe the bug Once I click on the icon (top right corner) that shows up roles, the list is empty

To Reproduce Once I click on the icon that shows up roles, the list is empty

Expected behavior List roles

Screenshots

Environment

  • OS: Mac os X 15.3.1
  • Browser Chrome 137.0.7151.57
  • Version 6.0

Additional context

Configuration has around 30 roles previously used properly before the upgrade.

Image

jorgemartineztala avatar Jun 06 '25 01:06 jorgemartineztala

Please push save button in the Configuraion screen because your internal database may be broken.

tilfin avatar Jun 06 '25 05:06 tilfin

@tilfin I have the same issue and this solution did not work for me. In fact, I can see the configuration is saved, I can see the list of credentials for different roles is kept in the extension config. FYI: Same versions for OS, browser and extension.

NickVasilev-dev avatar Jul 01 '25 07:07 NickVasilev-dev

It was the same for me after updating Chrome to 138.0.7204.158. But it started working again after I did a "manual" switch role.

hankwallace avatar Jul 23 '25 16:07 hankwallace

See #372 (this issue should be closed, I think)

f00f avatar Oct 30 '25 08:10 f00f

Why should it be closed? The issue is still ongoing. It's happening for me in Firefox and Chrome (logged in this morning). MacOs 26.0.1 on M4, Firefox About says up to date, Chrome just updated and relaunched. We have a workaround (go to us-east-1, switch, then go back), but that is not a fix and the issue is not resolved.

prowlaiii avatar Oct 30 '25 09:10 prowlaiii

Agreed, the problem is not resolved. I have it, too.

But another ticket for the same problem exists which has more comments, more info, and link to a PR. See link in my comment. There is no value in having this issue open.

f00f avatar Oct 30 '25 09:10 f00f

Why should it be closed?

because this ticket is a duplicate of #372.

AlexChesters avatar Oct 30 '25 09:10 AlexChesters

I haven't identified the root cause of the initial issue yet. However, a separate issue caused by the AWS Management Console update (from about 3 weeks ago) has been resolved.

tilfin avatar Nov 19 '25 16:11 tilfin