unable to log in on edge or google chrome

[willGG11]

Expected behavior

expected to log in on Wordplay Web as type in an email address

Actual behavior

receives "unable to log in prompt". And no email link was sent for logging in

Provide detailed steps that consistently reproduce the behavior, including any example code. If you can, make the steps as minimal as possible, finding the smallest possible set of steps that still produce the unexpected behavior.

1. Go to 'https://test.wordplay.dev/'
2. Click on 'login'
3. Type in email address
4. press the login button
5. receives "unable to log in prompt :("

Screenshots

Environment

What platform, OS, browser, and version are you using? Please be exact with version numbers, as different versions can result in a defect happening or not.

Desktop

• OS: v.12.4
• Browser Chrome
• Version: 117.0.5938.149
• Browser Edge

• Version: 118.0.2088.46

  the errors prompts: Failed to load resource: the server responded with a status of 400 () FirebaseError: Installations: Create Installation request failed with error "400 INVALID_ARGUMENT: API key not valid. Please pass a valid API key." (installations/request-failed). at DC (stores.9c84ff7c.js:3212:240) at async bU (stores.9c84ff7c.js:3227:481) at async DU (stores.9c84ff7c.js:3332:740) localhost:9099/ident…eymyfakeapikeymyf:1

  Failed to load resource: net::ERR_CONNECTION_REFUSED 9.17f40056.js:1 auth/network-request-failed 9.17f40056.js:1 Firebase: Error (auth/network-request-failed).

[amyjko]

Clarification: are you running locally the Firebase emulator (npm run emu) when you're doing this? If not, this is expected behavior, since there's no authentication backend. If you are running the emulator, or you're testing on the staging server (test.wordplay.dev), then this is a defect.

[willGG11]

Clarification: are you running locally the Firebase emulator (npm run emu) when you're doing this? If not, this is expected behavior, since there's no authentication backend. If you are running the emulator, or you're testing on the staging server (test.wordplay.dev), then this is a defect.

Confirmed: use both "test.wordplay.dev" and Firebase emulator( localhost:5173) to login and receive failed prompt

[amyjko]

Can you edit your OS information above? You specified a version but not an operating system.

[amyjko]

(Note: running the Vite dev server on localhost is not the same as running the Firebase emulator. To run the emulator, you have to explicitly run the command npm run emu).

[amyjko]

Tested with emulator and on https://test.wordplay.dev; cannot reproduce. Please provide your OS information and any information in the browser inspector console.

[willGG11]

I think we can close the issue just for now because I can not reproduce the issue either. I don't now the reason that cause the issue. I believe it might be the unstable internet connection from my end...

[amyjko]

Thanks for reporting @willGG11! Issues like this that depend on backend authentication infrastructure are always hard to test.

[amyjko]

I believe I found the cause of this: test.wordplay.dev was intermittently not receiving correct API keys, which was preventing login. This should be working now. @willGG11, can you confirm?

[willGG11]

confirmed: it is working now! :>

[amyjko]

Wonderful, thanks for confirming, and reporting.