Skip to content
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

Allow bundle task to be disabled for release #18892

Closed
wants to merge 3 commits into from

Conversation

deecewan
Copy link
Contributor

@deecewan deecewan commented Apr 17, 2018

Summary

The current system would always end up falling back to true for release builds

Test Plan

  • I ran my build after setting bundleInProductionRelease to false and noticed it still bundled.
  • I updated the code in react.gradle and ran my build again - this resulted in the correct behaviour
  • I removed the false setting and it correctly bundled.

A lot of logging revealed that when the bundleIn${targetName} flag was set to false, nothing actually changed.

Changelog

[ANDROID] [Fixed] Allow disabling of bundling for release builds

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 17, 2018
@deecewan
Copy link
Contributor Author

I'm not really sure why my builds are breaking. They are breaking on code that has nothing to do with my code.

Anyone have ideas?

The current system would always end up falling back to `true` for release builds
@deecewan
Copy link
Contributor Author

@janicduplessis sorry for the tag, but it looks like you've worked on this file before and I've seen you around the project.

I'm getting test failures that have seemingly nothing to do with the code I changed. In fact, I'm not sure how the code I'm changing could have possibly had an effect on test_android.

It seems like a pretty simple change - anything I can do to get it through?

@deecewan
Copy link
Contributor Author

@shergin any ideas on how I can get this through? as above, no idea why these tests would fail on this build.

@facebook facebook deleted a comment from pull-bot Feb 13, 2019
@facebook-github-bot facebook-github-bot added the Import Started This pull request has been imported. This does not imply the PR has been approved. label Feb 13, 2019
Copy link
Contributor

@facebook-github-bot facebook-github-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hramos is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@react-native-bot
Copy link
Collaborator

@deecewan merged commit 6b21109 into facebook:master.

@facebook facebook locked as resolved and limited conversation to collaborators Feb 13, 2019
@react-native-bot react-native-bot added the Merged This PR has been merged. label Feb 13, 2019
@hramos hramos removed Import Started This pull request has been imported. This does not imply the PR has been approved. labels Feb 14, 2019
slam pushed a commit to ubiquity6/react-native that referenced this pull request Sep 3, 2019
Summary:
The current system would always end up falling back to `true` for release builds
Pull Request resolved: facebook#18892

Differential Revision: D14069444

Pulled By: hramos

fbshipit-source-id: 16e32a366b3b2e252a98a967da827ba1ebaeff85
slam added a commit to ubiquity6/react-native that referenced this pull request Sep 3, 2019
Summary:
The current system would always end up falling back to `true` for release builds
Pull Request resolved: facebook#18892

Differential Revision: D14069444

Pulled By: hramos

fbshipit-source-id: 16e32a366b3b2e252a98a967da827ba1ebaeff85
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged This PR has been merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants