Yuchen Shi

We've updated the Emulator UI to address this in a previous version, so please update the Firebase CLI to the latest version just to make sure. Just let us know...

I'm not too familiar with the Docker caching mechanisms but could you please add a `RUN firebase --version` line right after and let me know the results? We can definitely...

Thanks for the additional info! Looks like the the colon `:` confused the Emulator UI or Firestore Emulator REST API and thus the subcollection IDs are not correctly listed. We...

~Fixed in v11.3.0.~

Whoops, wrong issue -- sorry for the confusion. We've fixed some other issues related to Emulator UI, not Emulator hub (used in `testing`).

While we work on this, I think a better workaround than downgrading Firebase CLI is specifying the hub address explicitly using IPv4: e.g. change the command: ``` firebase emulators:exec --only...

@kris-kolve-jumio Would you mind opening a different issue for the storage emulator timeout?

Hi all, we've updated how the emulator listens on ports in v11.14.2 and we believe it now should work for most cases (including the OP's repro, quickstart-testing, emulators-codelab, etc.) without...

@modosc Thanks for the follow-up. Would it be possible to get the full `firebase-debug.log`? We'd need to look into where this happens in context and see if we can find...

@modosc I have a guess on what's going on here -- the error may be happening with our new port detection logic and somehow IPv6 isn't available in your Docker...