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

Event listener is not fired when including android's back button during navigation between two apps #19711

Closed
Brynjulf opened this issue Jun 14, 2018 · 3 comments
Labels
Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@Brynjulf
Copy link

Brynjulf commented Jun 14, 2018

Environment

Environment:
OS: macOS High Sierra 10.13.5
Node: 8.9.0
Yarn: 1.3.2
npm: 6.1.0
Watchman: 4.9.0
Xcode: Xcode 9.4 Build version 9F1027a
Android Studio: 3.1 AI-173.4720617

Packages: (wanted => installed)
react: 16.0.0-beta.5 => 16.0.0-beta.5
react-native: ^0.55.4 => 0.55.4

Description

After successfully navigating from App1 to App2, and then moving back to App1 using Android's back button the url event listener does not fire. This causes problems when attempting to navigate to App2 again

componentDidMount() {
    Linking.addEventListener('url', this.handleOpenURL);
}

handleOpenURL(event) {
    store.dispatch(actions.linkingHandleUrl({ url: event.url }));
}

Steps to Reproduce

  • Navigate to App2
  • Go back to App1 using android's back button
  • Navigate to App2 again

Expected Behavior

Url event to still fire despite using android's back button as a part of the navigation

Actual Behavior

Event did not fire after using android's back button as a part of the navigation

@react-native-bot
Copy link
Collaborator

It looks like your issue may be missing some necessary information. Can you run react-native info and edit your issue to include these results under the Environment section?

@stale
Copy link

stale bot commented Sep 12, 2018

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.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Sep 12, 2018
@stale
Copy link

stale bot commented Sep 19, 2018

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.

@stale stale bot closed this as completed Sep 19, 2018
@facebook facebook locked as resolved and limited conversation to collaborators Sep 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Platform: Android Android applications. Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

3 participants