Uncaught TypeError in Firestore Emulator UI Requests Tab: Cannot read properties of undefined (reading 'method')

[JonahWhoDis]

Describe the bug
When accessing the Firestore Emulator UI's Requests tab at http://127.0.0.1:4000/firestore/requests, the page fails to load and displays a blank screen. The browser console shows an error: Uncaught TypeError: Cannot read properties of undefined (reading 'method') originating from react-dom.production.min.js and specifically within a component named TableRow.tsx.

To Reproduce
Steps to reproduce the behavior:
Remark: It only happens sometimes.

1. Start the Firebase Emulator Suite with Firestore enabled.
2. Open a web browser and navigate to the Firestore Emulator UI at http://127.0.0.1:4000/firestore.
3. Click on the 'Requests' tab to view Firestore requests.
4. Observe that the page does not load and instead displays a blank screen. The browser's developer console shows the mentioned TypeError.

Expected behavior
The 'Requests' tab should properly display the list of Firestore requests made by the application without any errors, allowing for debugging and monitoring of interactions with the Firestore emulator.

Screenshots
is attached

Desktop (please complete the following information):

• OS: Mac OS (14.1.1 (23B81))
• Browser Chrome
• Version Version 121.0.6167.85 (Official Build) (arm64)

Additional context
The issue persists even after updating Firebase tools to the latest version. It occurs across multiple browsers, indicating it's not browser-specific. Clearing browser cache and data does not resolve the issue. The error suggests a possible issue with the Emulator UI's handling of undefined properties in the Firestore requests display logic.

[mattiadevivo]

Hi @JonahWhoDis , I was experiencing the same problem.

In my case I used a Debian devcontainer with firebase-tools and openjdk-17-jre installed, I figured it out that some ERR_CONNECTION_REFUSED where appearing in the Firestore UI, as soon as I forwarded the 9150 port it started working properly, so my advice is to check whether the port is occupied by another process.