Plugin no longer works (empty account list)

[Gh0stExp10it]

Describe the bug
Difficult to describe what no longer works. Unfortunately, I haven't seen any entries/accounts in the plugin for some time now. Nothing has changed in my configuration for about 2 years.

My Config looks like this:

[organization1]
aws_account_id = 000011112222
region = eu-central-1

[org1-account1-admin]
aws_account_id = 123456789012
role_name = admin
source_profile = organization1
color = 5fbf77

Screenshots

Environment

• Chrome Browser

[ray-nichols-strat7]

After years of using this successfully I could not today.
I tried clicking option "Show only matching roles" (filters to only show profiles with roles that match your role in your master account.) - and it is working again.

[Gh0stExp10it]

After years of using this successfully I could not today. I tried clicking option "Show only matching roles" (filters to only show profiles with roles that match your role in your master account.) - and it is working again.

Thanks for the hint. Unfortunately this isn't working for me. The list is still empty, after I've checked the option "Show only matching roles".
For now and until this might be fixed, I'm using another Plugin with the name aws-role-switch (also open source on GitHub).

[erikpragt-connectid]

I've got the same, but clicking on the key icon twice "fixes" the issue: the first time the list is empty, the second time it's filled. I never had this issue before, but after moving to a new laptop (M3), this happens. I'm using Firefox 123.0.1 (64-bit).

[jacobb84]

I have the exact same issue, also right after I moved to a new laptop. Same version of Firefox as well, maybe there was an update? I thought I was going crazy ;-)

If it helps, I turned on debugging and saw this error when I first try to bring up the list:
Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
executeAction moz-extension://56ce359b-4d99-4e18-92e3-983ef3a348c4/js/popup.js:751

Line 751 is this function:
async function executeAction(tabId, action, data) {
return (chrome || browser).tabs.sendMessage(tabId, { action, data });
}

[jacobb84]

Naturally right after I posted I found this thread that fixed the issue for me: #330

[krymtkts]

I'm also facing the same issue.
It seems to have been fixed for now after save the configuration.

[AdrianSimionov]

Can confirm, clicking "Save" fixed the same issue for me, too!

[jstmrby]

My list also turned empty after some time of use, but I managed to fix it.
My solution was unrelated to the previous comments. I just misconfigured.
I'll leave my (silly) problem here:

Ever since I started using the extension I was logging in using the account ID: 000011112222
But this time around I entered the account alias without giving it a second thought: my-corpos-alias
This caused the extension to not recognize the account.

Easily fixed by adding both the account ID and alias to my source profile.

[my-corp]
aws_account_id = 000011112222
aws_account_alias = my-corpos-alias

[myrole @ partner]
aws_account_id = partner-alias
role_name = myrole
source_profile = my-corp