-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
## Environment #4401
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
|
This issue is closed, If you have any questions, you can comment and reply. |
h |
Environment
Description
I first noticed this while working in an out-of-tree platform, React Native MacOS. Running
npx react-native run-macos
did not start Metro automatically. Filed the full set of details originally in their project at microsoft/react-native-macos#2208But I got a notificaiton about the "removing run on iOS/Android key handlers" discussion about this comment: react-native-community/discussions-and-proposals#821 (comment)
And I thought it might be related to what I had seen on React Native MacOS.
Reproducible Demo
Follow the React Native macOS setupd (for the most part, the current docs are actually a little out of date, but this will be the steps for an up-to-date RN project)
The app will build, but not start Metro:
Not a big deal, I can just run
yarn start
, then tap "reload"Everything works great from there. I also did not have this issue when following the instructions for RN 0.71:
Reproducer repo: https://github.com/coolsoftwaretyler/rnms-issue-repro
It sounds like this is happening on in-tree platforms as well based on @Rexogamer's comment in that discussion post, but I don't have a reproduction for that at the moment.
Thanks for your work and consideration!
Originally posted by @coolsoftwaretyler in react-native-community/cli#2530
Originally posted by @nand16041987 in trustwallet/assets#29351
The text was updated successfully, but these errors were encountered: