[FirebaseAuth]: Reopen: Emulator in development doesn't work after logged in / Loading use from session storage..

[matanshukry]

Is there an existing issue for this?

• I have searched the existing issues.

Which plugins are affected?

Auth

Which platforms are affected?

Web

Description

In the past I've created this issue: #11534 , which apparently the cause was this: #11233.

I have tested now and it reproduced, and while I was trying to talk to local emulators, it kept talking to prod. I could notice the following while debugging: The call to useAuthEmulator skipped due to the condition if (origin == emulatorOrigin) {, which evaluated to true.

Anyway after clearing storage data through browser "inspect" -> Application, it worked. so the problem has apparently re-surfaced.

Reproducing the issue

See previous issue - it's the same thing.

Firebase Core version

4.14.0

Flutter Version

3.47.2

Relevant Log Output

Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments

No response

[SelaseKay]

Hi @matanshukry, thanks for the report. I'm looking into this.

[SelaseKay]

Hi @matanshukry, thanks again for the report.

Confirmed on web: after a reload, sessionStorage still has http://host:port from the last run, but the JS Auth instance is new and still on production. useAuthEmulator treated that leftover string as “already connected” and returned without calling connectAuthEmulator. Clearing Application storage worked because it wiped both the sticky note and the persisted user.

That skip is also why 127.0.0.1 was especially broken — plugin init only reconnected when hostname == 'localhost'.

Fix is in #18690: skip only if this Auth instance is already on the emulator, and reconnect on 127.0.0.1 / [::1] as well.

Thanks!

[matanshukry]

@SelaseKay nice, that was super fast, both the review and the fix! Thank you 💯