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

Message "Failed to fetch user info from the AWS Management Console page" in first click #318

Closed
hramos8 opened this issue Oct 27, 2023 · 2 comments · Fixed by #321
Closed

Comments

@hramos8
Copy link

hramos8 commented Oct 27, 2023

Describe the bug
Every first time I click on the plugin after entering the AWS console page, I receive the message "Failed to fetch user info from the AWS Management Console page." The same thing happens when I go to the page of another service within the same account (e.g., EC2). On the first click, the error message appears, and on the second click, the list is loaded correctly. I noticed this bug after the last update.

To Reproduce
Steps to reproduce the behavior:

  1. Log on AWS console
  2. Click on the plugin button (the error message appears)
  3. Click again on the plugin button (the list is loaded correctly)
  4. Go to the EC2 service
  5. Click on the plugin button (the error message appears)
  6. Click again on the plugin button (the list is loaded correctly)

Expected behavior
The list appear in first click

Environment

  • OS: Windows 11
  • Browser firefox 118.0.2 (64-bits)
  • Plugin version: 4.0.0
@tilfin
Copy link
Member

tilfin commented Oct 28, 2023

At the time of the first click on the plugin icon, the AWS Management Console page load has not finished, so the account information cannot be taken and an error occurs. If you wait a bit and then perform the first click, you will not get an error. The initial loading of the plugin popup process may have speeded up since version 4, making that event more likely to occur.

I will try to find a way to make it less likely to happen.

@tilfin
Copy link
Member

tilfin commented Nov 7, 2023

@hramos8 I found the cause of this problem. https://discourse.mozilla.org/t/are-content-scripts-not-automatically-injected-anymore-with-manifest-v3/108146

  1. Open about:addons (Manage Your Extensions)
  2. Select AWS Extend Switch Roles
  3. Select Permissions
  4. Turn on the domains you use in Optional permissions for added functionality.

@tilfin tilfin pinned this issue Nov 7, 2023
@tilfin tilfin unpinned this issue Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants