Firefox unable to load account list from graphql api

[jvanenckevort]

Describe the bug
Our end-users complain about not being able to load the account list on Firefox. We have reproduced this issue and it seems to be working on Chrome just fine.

To Reproduce
Steps to reproduce the behavior:

1. Go to the 'Create request' page
2. Click on the account list
3. Account list is not loaded
4. Open developer mode and you'll see the following error:

GET wss://xxxxxxxxxxxxxxxxx.appsync-realtime-api.xx-xxxx-x.amazonaws.com/graphql NS_ERROR_NET_RESET

Firefox can’t establish a connection to the server at wss://xxxxxxxxxxxxxxxxx.appsync-realtime-api.xx-xxxx-x.amazonaws.com/graphql.

Expected behavior
The account list should be loaded within a few seconds, it usually tends to take between 2 and 5 seconds.

Screenshots
None

Desktop:

• OS: macOS
• Browser: Firefox 138.03
• Version: 1.3.0

Additional context
We have a workaround for people not to use Firefox to access AWS Team, but this is annoying because you would have to keep sessions in multiple browsers.

[wapa-soptim]

Same error with Firefox Versions 128.10.1esr.
Workaround for us: Version 136.0.3240.76 (Official build) (64-bit) - still working.

[jvanenckevort]

Firefox version 138.03 is not working

[barnabycollins]

Not sure if an update was pushed or not, but this seems to be working for me today having been broken yesterday on the same Firefox version (138.0.4, Apple silicon macOS).

[wapa-soptim]

Not sure if an update was pushed or not, but this seems to be working for me today having been broken yesterday on the same Firefox version (138.0.4, Apple silicon macOS).

Can only speak for us: Still broken.
Working for us again as well (as of 23-05-2025).

We can't find the root cause of this error - maybe AWS changed smth. on their backend? Sure feels like on our end; this happend little by little, like with a migration, where it depends on which node you land.
Let us see what happens the next couple of days but we are not able to provide any fix.

[su-mskiles]

I'm running into this same issue with my own Amplify project running Firefox 139.0.1. Happens intermittently on multiple computers and networks. I'm not able to provide reliable reproduction steps. Clearing cache/cookies sometimes resolves the issue, sometimes doesn't.

[LouPritch]

Just to echo the previous comments, we are also experiencing the same issue. We haven't yet found a way to reproduce the error on demand and it is only specific to the latest Firefox versions.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.