It looks like you are using an older version of React Native. Please update to the latest release, v0.58 and verify if the issue still exists.

The "⏪Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.

I've been running into the same issue for awhile now. Seems to be happening as well for 0.58.3.

+1

I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while.

If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.

I experience this issue too

I added a repo with react-native init that reproduces the issue https://github.com/ferrannp/react-native-elevation-animation-android-pie.

Hi i'm experiencing this issue as well on Android Pie only (earlier versions are fine), any suggestions on work arounds?

I'm experiencing this issue too. Does anybody found a workaround for this issue?

Is anyone working on this? We are facing the same issue

Also facing this issue, any solution?

damn this is bad, never thought it would be like that , for now I can't use elevation because it leave the shadow for a little while , when the opacity goes to 0

I'm also facing this issue. Does anyone know any workaround? Especially annoying when I'm trying to animate a box with several buttons inside it, the shadows appear before the buttons do.

@fabriziobertoglio1987 The child needs to have elevation.

<Animated.View style={{ opacity: animatedOpacityValue }}>
  <View style={{ width: 100, height: 100, backgroundColor: 'pink', elevation 5 }} />
</Animated.View>

This is the easiest way to reproduce

happening on 0.62.2

happening on 0.63.1

I experienced it a few times in different react-native version, also in react-native 63.0
What works for me is using react-native-shadow in such cases which creates fake SVG shadow 😎
Warning: it doesn't look the same as a native shadow, but in my opinion pretty good. Maybe use an original one for iOS and react-native-shadow for Android

For example

          <BoxShadow
            setting={{
              border: 2,
              color: '#000',
              height: 400,
              opacity: 0.25,
              radius: 10,
              width: Dimensions.get('window').width - 40,
              x: 0,
              y: 3,
            }}
          >
            <View
              style={{
                flex: 1,
                paddingHorizontal: 40,
                paddingVertical: 30,
                backgroundColor: 'white',
                borderRadius: 10,
              }}
            >
                  // your content
            </View>
          </BoxShadow>

This is how it looks eventually on Android:

@CyxouD Thank you for the workaround, i will keep it in mind for when shadows are a necessity. It's such a pity, Neumorphism employs shadows a lot and i'm facing such a scenario but i will keep it in mind. The main issue is with react-navigation to be honest but what can you do : /

@CyxouD I believe it can be edited in the setting prop so it looks more natural maybe even more than the elevation.

My issue:
react-navigation/react-navigation#8676

On android, setting a view's opacity will render artifacts when child views have elevation.

So I've investigated this issue and came to the conclusion, that this is an android intended behavior.

Background:

<View style={{opacity: 0.5}}>
	<View style={{elevation: 5, margin: 10, backgroundColor: 'red'}}>
<View>

To understand this issue we let's dig into react code. Both views will get a BaseViewManager, which holds a reference to a ReactViewGroup.ReactViewGroup subclasses a ViewGroup and not an Android View (because it can have children). When setting a backgroundColor to a ReactViewGroup it creates a ReactViewBackgroundDrawable which subclasses a Drawable and sets it as background. The creation happens in getOrCreateReactViewBackground which composes any already existing background drawable (maybe images use this, in all my test cases the existing drawable was always null) with the new background using LayerDrawable.

Problem:
Now when setting an alpha value (changing opacity) it will do this on the ReactViewGroup directly but not on the background drawable, which is why we have the artifact. As react-native per default set hasOverlappingRendering to false to save memory, this problem is an expected android performance optimization. It seems that some devices do not perform the optimization and I only experienced this when changing the alpha after the first render. See android docs for what this flag does.

In the screenshot below you can see the different parameters (plain android project in this repo, not react-native, although I used the same ReactViewBackgroundDrawable class from react-native which I just extracted and patched to get it running).
There are 6 red 100x100 boxes that get the opacity set on their view or for testing purposes on their background drawable. Within a red box a yellow box is placed with elevation set to 10. In the first row, hasOverlappingRendering is disabled.

Repo: https://github.com/DomiR/react-native-opacity-issue
So as you can see on both boxes on the right-hand side setting opacity only on the background is not enough, as all children will still have full opacity. Setting alpha both on the background and on the view itself will result in 0.25 opacity for the background. On the left-hand side is what we really want but we need to hasOverlappingRendering enabled like in the left bottom.

Solution:
I don't know if there is a solution that is good for everyone.
As you can see from the screenshot we need to set hasOverlappingRendering but doing so per default is not performant (facebook blog entry).

Fortunately, we can set this flag using needsOffscreenAlphaCompositing as a view prop.

As @kmagiera mentioned that you should probably enable this only temporarily during animations.
The react-native docs also mention using renderToHardwareTextureAndroid in combination.

PS: What also should work is setting the opacity value for all children as well.

what about option "renderToHardwareTextureAndroid" for View?

Thanks @DomiR , can confirm that setting needsOffscreenAlphaCompositing on the animated view seems to solve the issue.

Before:

After:

PR example.

Any updates?

So the trick is to set the elevation to 0 until fade-in animation is complete for the view.
elevation:fadeAnim==1?5:0
Work's perfectly for me.

Several users tested a workaround (needsOffscreenAlphaCompositing) for this issue (more info in #23090 (comment)). I believe this issue is solved.