Skip to content

Fix deeplink not handled correctly due to navigator initialization problem. #5032

Martin Santangelo requested to merge js/deeplink-coldstart-handling into develop

Ticket(s) / Related Merge Requests

#5032 (closed)

Summary of Changes

The navigator was firing the onReady event before it was actually ready. It seems like the providers were not rendering the children on the first render.

We will need to be super careful when adding new providers to the App component. It is preferred to add them before the Navigator container to prevent this kind of issues

  • Changelog file updated with this template (one or more)
    • Added for new features.
    • Changed for changes in existing functionality.
    • Deprecated for soon-to-be removed features.
    • Removed for now removed features.
    • Fixed for any bug fixes.
    • Security in case of vulnerabilities.

Testing Considerations

Tap on a supermind request email with the app closed (Cold start)

Regression Scope

initial navigation handling

Platform Affected (web, mobile, etc)

Reported on iOS but it may affect other devices

Developer Testing Completed

Android / iOS

Screenshots

VID_20230628_174052

Does this impact

  • Localization
  • Dark/light mode
  • Guest mode

Merge request reports