-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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
Do not run packager in Release mode #23938
Conversation
Since the diff is hard to read, I only added: && [ \"$CONFIGURATION\" == \"Debug\" ] ; to the After changes, it's: if [ -z "${RCT_NO_LAUNCH_PACKAGER+xxx}" ] && [ "$CONFIGURATION" == "Debug" ] ; then |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
omg thank you, that was so annoying when I tried this the last time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpojer is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
This pull request was successfully merged by @grabbou in 581711c. When will my fix make it into a release? | Upcoming Releases |
Summary: When running your project in "Release" mode, Metro will start automatically. This is not desired. See react-native-community/cli#31 for details [IOS] [FIXED] - Do not start Metro in Release mode Pull Request resolved: #23938 Differential Revision: D14477595 Pulled By: cpojer fbshipit-source-id: 05166537500fa95a59ae87f27154c9665b7ccfe8
Changes from this PR are reverted back with this commit. Was it a mistake? |
That looks like a mistake. CC: @lucasbento @cpojer the diff in linked PR removes check for |
Oh yeah, totally missed this when reviewing. Sorry about that! @deepsweet could you send a PR to bring this back? |
I'll open a PR to fix this, sorry! |
PR #24929, thanks for checking this @deepsweet! |
Summary: This PR fixes a regression introduced on [3273d23](3273d23#diff-883359f85083d00b7266ec2acebcca9f) that removed #23938. It also adds the check for `React` and `React-tvOS` targets. ## Changelog [IOS] [FIXED] - Do not run packager in Release mode Pull Request resolved: #24929 Differential Revision: D15391692 Pulled By: cpojer fbshipit-source-id: c2e524108be3bf1e45b0d0ff7cddd9785b51a60f
Summary: This PR fixes a regression introduced on [3273d23](facebook@3273d23#diff-883359f85083d00b7266ec2acebcca9f) that removed facebook#23938. It also adds the check for `React` and `React-tvOS` targets. ## Changelog [IOS] [FIXED] - Do not run packager in Release mode Pull Request resolved: facebook#24929 Differential Revision: D15391692 Pulled By: cpojer fbshipit-source-id: c2e524108be3bf1e45b0d0ff7cddd9785b51a60f
Thank god this worked. This was driving me crazy for hours. Kudos. |
Summary
When running your project in "Release" mode, Metro will start automatically. This is not desired. See react-native-community/cli#31 for details
Changelog
[IOS] [FIXED] - Do not start Metro in Release mode
Test Plan
Run RNTester in Release mode - packager doesn't start anymore