-
Notifications
You must be signed in to change notification settings - Fork 900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hosting emulator defaults to a port that's not open by default in macOS Monterey #3875
Comments
Thanks for tracking this down and reporting it! Folks like me who aren't interested in AirPlay can turn it off from System Preferences, Sharing, and then uncheck the checkbox titled "AirPlay receiver". Then Firebase hosting on port 5000 works again. |
Hmm, that is really annoying. Since we've set the precedent of using port 5000 for most of a decade I would be inclined to simply provide a better error if we encounter a port conflict on Monterey. |
Hi Team, I got this error when I start the emulators on Monterey, it was working on BigSir
I found a solution to change the firebase.json, like
It can launch the emulator, but the callback function is not working, like firestore callback when an object is added. Any idea on this? Thanks |
@jessejiang0214, you saved my day! |
Hi @v1ct0r change host just can launch the emulator, but the callback function for the emulator is not working. |
This worked. thank you very much! |
I have similar log, but change host to 0.0.0.0 still didn't work for me. |
I've created an internal bug b/211308357 to track this issue. As @abeisgoat mentioned, improving the error message might be the resolution here. |
Potential Workaround - for those who just want to run hosting locally - there is a port flag on the serve command you can use: |
Fixed in #4415 |
[REQUIRED] Environment info
firebase-tools: 9.21.9
Platform: macOS 12.0.1 Monterey, MacBook Pro (14-inch, 2021)
[REQUIRED] Test case
[REQUIRED] Steps to reproduce
firebase-tools
firebase emulators:start
It seems as if this is an issue because the new version of macOS has an "AirPlay receiver" feature which allows you to AirPlay to a Mac device, and this listens on port 5000. Obviously this can be worked around by disabling the feature or changing the emulator hosting port in the firebase config, but the feature comes on by default so I imagine a lot of people will be running into this as they upgrade to the latest OS.
[REQUIRED] Expected behavior
Emulator should start without having to disable AirPlay receiver or changing the default port.
[REQUIRED] Actual behavior
The firebase hosting emulator won't start until you disable AirPlay receiver, or the hosting port.
The text was updated successfully, but these errors were encountered: