-
Notifications
You must be signed in to change notification settings - Fork 620
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
Inconsistent Release Mode Behavior in External Module (native-base) #277
Comments
I am also experiencing this issue. |
@mjesun this looks like another Babel issue... @ajmath: for release builds we started to use extensively Babel to perform dead code elimination. It seems that in some situations Babel does not track some scope changes correctly and this leads to issues like this one. It would be cool if you could find some minimal code that causes wrong logic during release so we can report it to Babel |
The two places we were seeing issues was with native-base and the aws-sdk and both have been addressed with fixes in those libraries: https://github.com/aws/aws-sdk-js/blob/master/CHANGELOG.md#22861 I haven't seen any other issues yet so I'm happy to close this, but I'm a bit concerned about it popping up again in the future. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Release builds are exhibiting various feature breaking issues that aren't present in debug builds. The following errors have been observed and reproduced when using native-base components.
<Input/>
element does not honorsecureTextEntry
oronChangeText
props<Item/>
element does not honor thefloatingLabel
propIf the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.yarn install
yarn react-native run-android
to test the dev buildyarn react-native run-android --variant=release
to test the release buildThe issue is also present in iOS builds but the android builds are easier to test in release mode.
What is the expected behavior?
Components have the same behavior in dev and release builds
Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
See more details in the package.json of the bug reproduction repository https://github.com/ajmath/ReleaseRenderIssue/blob/master/package.json#L9
The text was updated successfully, but these errors were encountered: