Skip to content
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

[Android | iOS] componentDidDisappear's performance is inconsistent in Android and iOS when App slides to background #7841

Open
1 task done
YadongChen opened this issue Feb 2, 2024 · 0 comments

Comments

@YadongChen
Copy link

What happened?

(1)Use the code of the current main branch and run it using the example in the playground

(2)Slide the Playground App to the background:AppState.active => AppState.background,Then return to active state:AppState.background => AppState.active

(3)For iOS:No Screen Lifecycle will be triggered

(4)For Android:componentDidDisappear will be triggered

  1. AppState.active => AppState.background:
  • componentDidDisappear: Component2
  1. AppState.background => AppState.active:
  • componentWillAppear: Component2
  • componentDidAppear: Component2

What was the expected behaviour?

Inconsistent behavior in Android and iOS, is this the intended design?

I didn't find the relevant documentation description or related issue. I'm not sure if it is a problem?

Was it tested on latest react-native-navigation?

  • I have tested this issue on the latest react-native-navigation release and it still reproduces.

Help us reproduce this issue!

No response

In what environment did this happen?

React Native Navigation version: 7.37.2
React Native version: 0.72.3
Has Fabric (React Native's new rendering system) enabled: (yes/no) no
Node version:v20.10.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant