[Android] Cannot toggle pointerEvents + opacity on View

[joncursi]

I am trying to toggle an Overlay in and out over scene content. The below code works perfectly on iOS but will not show the overlay at all on Android. According to the react-native documentation:

• pointerEvents should work for both platforms,
• as should opacity.

Thoughts?

import { View } from 'react-native';

...

<View
  pointerEvents={condition ? 'auto' : 'none'}
  style={{
    opacity: condition ? 1 : 0,
  }}
>
  <Text>This toggles properly on iOS, but never displays on Android. Bug?</Text>
</View>

I originally spotted this while attempting to animate via react-native-animatable (please see oblador/react-native-animatable#57), but since the same issue is present on the normal View component, I believe this may be an issue with react native itself.

[gre]

How is your view an overlay? I don't see any position: absolute , but if you use that position: absolute you might also need to provide width and height unlike in iOS.
I've notice this difference when porting from iOS, the content seems to be overflow hidden otherwise.

[joncursi]

I stripped out all other styles for simplicity of the example, as I was able to narrow down the issue to the pointerEvents + opacity combination on Android. I have tried absolute positioning with calculated height and width, it doesn't change the result.

[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.