The ART '<Surface>' becomes invisible in Android

[alwaysonlinetxm]

Is this a bug report?

Yes.

Have you read the Contributing Guidelines?

Yes.

Environment

Environment:
OS: macOS Sierra 10.12.6
Node: 8.4.0
Yarn: 1.3.2
Watchman: 4.9.0

Packages: (wanted => installed)
react-native: 0.50.1 => 0.50.1
react: 16.0.0 => 16.0.0

Target Platform: Android 7.1.1

Steps to Reproduce

1. generate a pathh and draw if with ART, it works correctly on the first render;
2. put the phone to sleep;
3. awake the phone;
4. the <Surface> area becomes invisable;

Expected Behavior

it should just look like same with the first render.

Actual Behavior

the <Surface> area becomes invisable;

Reproducible Demo

the main just like below:

<Surface width={ 300 } height={ 200 }>
  <Shape  d={ new Path()
      .moveTo(0, 0)
      .lineTo(0, 200)
      .lineTo(300, 200)
      .lineTo(300, 0)
      .close() } fill={ '#f00' } />
</Surface>

[cyuanyang]

me too. if you refresh ui ,it good work. how did you solve it?

[ardmn]

Same issues . I think the maintainers are have only iOS devices and don't want support android. I think they do work on react-native only because they likes write code on js for iOS.

[react-native-bot]

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

_{How to Contribute • What to Expect from Maintainers}

[nolan-m]

I updated to React Native 0.53.3 and still have this issue.
I tried to call this.forceUpdate as a work around and still did not work.

[woowalker]

em, what i face is ,when i use animated on Surface, like
const AniSurface = Animated.createAnimatedComponent(Surface)
<AniSurface style={{transform: [{translateX: this.state.aniTransX}]}}/>
when the animation start the Surface panel invisible, all dark like
but, when i open the dev menu, and click Toggle Inspector, the Surface visible again
=====UPDATE 2018.03.05=====
set style backgroundColor on the top View(not always top View, but must parent View), the Surface always visible

[ghostrick]

me too.
I call this.forceUpdate, But the situation is not improved.

[spaceye]

Same here. We ended up changing component's key value to force remount on active app state change and device rotation (AppState and Dimensions event listeners).

[anthony-skr]

I'm facing the same problem. I will probably use the same fix (like there bartgryszko/react-native-circular-progress@f198080).

I don't get why this issue has been closed... it makes ReactNative ART on Android unreliable.

[patrickkempff]

I am also having this problem, ended up using the AppState solution. This bug makes ART almost unusable on Android. I hope to investigate it a bit further next week when i have some spare time.

CC: @btegenbosch

[ghostrick]

I still have similar problems.
When will this problem be improved?
Also, what is the most effective solution? 🤔

[sophiebits]

Results from an internal investigation here:

From API level 25 onwards the hardware layer is deleted with the below call stack


Screen on -> TextureView's draw gets called --

boolean createNewSurface = (mSurface == null);
if (createNewSurface) {
// Create a new SurfaceTexture for the layer.
mSurface = new SurfaceTexture(false);
nCreateNativeWindow(mSurface);
}
mLayer.setSurfaceTexture(mSurface);

So, if there is a surface existing from before sleep, use that. A regular Textureview proceeds to draw on preexisting surface and has no problem.

In the case of ARTSurfaceView we are doing all the drawing here -

https://github.com/facebook/react-native/blob/v0.55.4/ReactAndroid/src/main/java/com/facebook/react/views/art/ARTSurfaceViewShadowNode.java#L61

(Oh btw, Android says not to actually - Subclasses of TextureView cannot do their own rendering with the {@link Canvas} object.)

So, ARTSurfaceView is not aware of the whole sleep and destroy, there is no redraw after screen gets switched on and hence the blank screen.

It sounds like the best path forwards may be to switch from TextureView to SurfaceView since the latter appears intended for software drawing which is what we're doing (vs video/camera use cases recommended in TextureView docs).

It's not clear if we'll have time to work on this at FB soon but if someone in the community wants to try their hand at making the switch then that would be valuable towards getting this bug fixed.

cc @himabindugadupudi

[AricWu]

Same issues , and I did a test on the latest ‘react-native-0.55’ that was not resolved. This problem directly led to my failure to use ART in my projects, but I found that a third-party framework 'react-native-svg' did not have this problem when used.

[jh3141]

Why was this closed again? AIUI the bug still exists in the latest version ...

[AricWu]

They write release notes say they have resolved it in 0.54.And I test the bug in react-native-0.54 ,0.55 ,still exists.

[sophiebits]

The commit fixing it had to be reverted due to another bug. Hopefully we will be able to land it again for a permanent fix.

[ap050492]

How to set click event of shape area in react native ?

I need write click event of particular Shape which draw using react native ART. How can i achieve this ?
can you please share your ideas or thought on this so can i worked on it.

sectionAngles.map(section => (
                <Group>                

                <TouchableWithoutFeedback                  
                  onPress={this.bindCallBackClick}>
                  <View>
                  <Shape
                    key={section.index}
                    d={path(section)}
                    fill={section.data.color}
                    strokeWidth={1} />
              
                  <ART.Text font={{ fontFamily: 'Helvetica Neue', fontSize: 20, }}
                    fill="#000"
                    x={path.centroid(section)[0]}
                    y={path.centroid(section)[1]}
                    ellipsizeMode={"middle"}
                    alignment="center"
                  >{section.data.itemName}</ART.Text>
                  </View></TouchableWithoutFeedback>
                </Group>

              ))

[JohnRyanTsai]

Same problem,How to solve this?

[robinclaes]

Same problem here.

[cabelitos]

Hello everyone I created a pull request that fix this issue, if possible could you guys take a look? Thank you very much #22624

[ksincennes]

Hello, are there any updates on this? Is it planned for the next release of React Native or would it be better to make a fork and fix it there?

[cpojer]

We just merged the PR that is supposed to fix this issue, to be shipped with 0.61.

[baragatti]

While 0.61 isn't released yet, I've done a workaround solution that isn't perfect but works.
I've created a Surface class that updates it key when going foreground, then React Native lifecycle will destroy and create the instance.

import React from 'react';
import {
  AppState,
  ART,
  ARTSurfaceProps,
} from 'react-native';

const { Surface: RNSurface } = ART;
const uuid = () => Math.random().toString(36).substring(2) + (new Date()).getTime().toString(36);

export default class Surface extends React.Component<ARTSurfaceProps> {
  constructor(props) {
    super(props);

    const propKey = props.key || 'surface';

    this.state = {
      key: `${propKey}-${uuid()}`,
      propKey,
      appState: AppState.currentState,
    };
  }

  componentDidMount() {
    AppState.addEventListener('change', this.handleAppStateChange);
  }

  componentWillUnmount() {
    AppState.removeEventListener('change', this.handleAppStateChange);
  }

  static getDerivedStateFromProps(nextProps, prevState) {
    const propKey = nextProps.key || 'surface';

    if (propKey !== prevState.propKey) {
      return {
        key: `${propKey}-${uuid()}`,
        propKey,
      };
    }

    return null;
  }

  handleAppStateChange = (nextAppState) => {
    const {
      appState,
      propKey,
    } = this.state;

    if (appState.match(/inactive|background/) && nextAppState === 'active') {
      this.setState({ appState: nextAppState, key: `${propKey}-${uuid()}` });
    } else if (appState === 'active' && nextAppState.match(/inactive|background/)) {
      this.setState({ appState: nextAppState });
    }
  };

  render() {
    const { key } = this.state;

    return (
      <RNSurface
        key={key}
        {...this.props}
      />
    );
  }
}

[taoqf]

When will 0.61 be released?

[duccyf]

@baragatti, It worked. Thank you.

[HideOnBushTuT]

While 0.61 isn't released yet, I've done a workaround solution that isn't perfect but works.
I've created a Surface class that updates it key when going foreground, then React Native lifecycle will destroy and create the instance.

import React from 'react';
import {
  AppState,
  ART,
  ARTSurfaceProps,
} from 'react-native';

const { Surface: RNSurface } = ART;
const uuid = () => Math.random().toString(36).substring(2) + (new Date()).getTime().toString(36);

export default class Surface extends React.Component<ARTSurfaceProps> {
  constructor(props) {
    super(props);

    const propKey = props.key || 'surface';

    this.state = {
      key: `${propKey}-${uuid()}`,
      propKey,
      appState: AppState.currentState,
    };
  }

  componentDidMount() {
    AppState.addEventListener('change', this.handleAppStateChange);
  }

  componentWillUnmount() {
    AppState.removeEventListener('change', this.handleAppStateChange);
  }

  static getDerivedStateFromProps(nextProps, prevState) {
    const propKey = nextProps.key || 'surface';

    if (propKey !== prevState.propKey) {
      return {
        key: `${propKey}-${uuid()}`,
        propKey,
      };
    }

    return null;
  }

  handleAppStateChange = (nextAppState) => {
    const {
      appState,
      propKey,
    } = this.state;

    if (appState.match(/inactive|background/) && nextAppState === 'active') {
      this.setState({ appState: nextAppState, key: `${propKey}-${uuid()}` });
    } else if (appState === 'active' && nextAppState.match(/inactive|background/)) {
      this.setState({ appState: nextAppState });
    }
  };

  render() {
    const { key } = this.state;

    return (
      <RNSurface
        key={key}
        {...this.props}
      />
    );
  }
}

Thanks !!!!!! It works . you did help a lot