Android Modal style issues Samsung Galaxy S5/S6

Description

I’ve faced really strange issue happening on Samsung devices (Galaxy S6/S7 Android 6.0.1, other not tested) ONLY. I’m using react-native Modal components in the app, and each component has a button at the bottom of the page (to confirm some action). This button has style flex: 1 applied to it with parent container styles as: justifyContent:"space-between". So the button is placed at the very bottom of the screen. On every platform it works great, except Samsung devices, starting from SECOND application run. I mean, that for the first time it renders correctly, but after u close the app (delete from running processes) and run it again – the button just disappears. Again, it’s not happening neither on IOS nor on any other Android device (for sure, emulators too). This issue doesn’t exist for a regular pages, only for Modal ones. I suspect that this may be a mix of Modal component bugs and Samsung devices, providing their custom launcher.

Reproduction

Currently I’m using react-native: 0.35.0 and tried to upgrade to 0.36, 0.37, 0.38 – none of those fixes the issue. Because of large project, lots of deps and strict timeframe I cannot upgrade to >=0.39 as it causes too many issues. Playing with styles also doesn’t give me any effect, until I place this button to be NOT the last element inside the container View, which doesn’t suit to my needs, as it should be at the very bottom of the page

Please help me to resolve this issue. Thanks.

Additional Information

• React Native version: 0.35, 0.36, 0.37, 0.38
• Platform: Android
• Operating System: MacOS
• Dev tools: Android Studio 2.2.2

[arsenslyusarchuk]

@hramos Hello. This issue disappeared after system update on Samsung Galaxy S5/S6

[hramos]

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we’re automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

• Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
• If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
• Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.