Fix macOS Monterey obscure bugs #151
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Visit the preview URL for this PR (updated for commit 2efe5f2): https://carpooling-6112a--pr151-fb-monterey-emulator-8pgiih4e.web.app (expires Wed, 02 Mar 2022 21:09:29 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 |
CobeyH
approved these changes
Feb 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing some very obscure issues that only affect macOS Monterey when running Node 17 and firebase emulators that took me a while to figure out.
Summary: the latest version of macOS rewrites localhost to ipv6 address
::1instead of127.0.0.1as it has always been, and firebase emulators don't expect that and timeout waiting for their requested ports. Also macOS now uses port 5000 for AirPlay despite its popular use by developer tools.Further reading: Firebase Localhost Issue and macOS port issue