-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
Linking.openURL
within Headless JS task will remount the entire app
#21610
Comments
Can you run If you believe this information is irrelevant to the reported issue, you may write |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
I'm not sure how to make a reproduction case for this, @rcidt - is there any chance you can make something simple, it'd make it much easier to diagnose |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information. |
Environment
Description
I am starting a Headless JS task when I receive a push notification when the app is in not in foreground. In my Headless JS task I perform some logic and then I will use
Linking.openURL('myapp://myapp')
to launch the app.In cases where the app is running in the background, the
Linking.openURL
will bring the app to foreground, but it will remount the entire app, as if I was launching it for the first time.This would be fine, as long as the "old" app to be unmounted, but it's as if the "old" app is also running, so all my event listeners and react lifecycle methods run double. As if I was running two instances of the app simultaneously.
The text was updated successfully, but these errors were encountered: