App: [$500] Android - Deeplink navigation does not work for RHN links.

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

Action Performed:

  1. Open the app on Android.
  2. Log out if already logined.
  3. Use deeplink new-expensify://settings/profile/personal-details/date-of-birth. Please use the domain/scheme that works for you. you can also use staging url if testing staging app.
  4. Now, login with a user.
  5. Notice that user is not taken to deeplink page.

Expected Result:

Deeplink for RHN should take the user to that page after login.

Actual Result:

RHN deeplinks does not open after sign in when opened while user is log out.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.67.2 Reproducible in staging?: y Reproducible in production?: y If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs: https://stackoverflow.com/c/expensify/questions/4856 Notes/Photos/Videos: Any additional supporting documentation

https://github.com/Expensify/App/assets/93399543/fd077a6a-7b4b-4ecc-8df6-2391965c04bc

Expensify/Expensify Issue URL: Issue reported by: @parasharrajat Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694080489810799

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01f1e03cd76963690d
  • Upwork Job ID: 1701262065942163456
  • Last Price Increase: 2024-03-18

About this issue

  • Original URL
  • State: closed
  • Created 10 months ago
  • Comments: 85 (56 by maintainers)

Most upvoted comments

Yeah, let’s go forward with that then

@thienlnam I could take a look today, but from tomorrow (22.12) I’m OOO till 2.01.24.

No, I don’t see that we need further proposals on this one. The PR for this one has been in production for 2 weeks.

This one is done.

@abekkala I don’t think so. The revert PR is merged https://github.com/Expensify/App/pull/29706#event-10669880085 before Melvin said the PR https://github.com/Expensify/App/pull/28278 deployed to Prod https://github.com/Expensify/App/issues/27168#issuecomment-1765301341 => I believe we can reproduce this issue in current Prod/Staging.

There are 2 issues that waiting for this issues get resolved:

Hey, it’s Lucas from Callstack. Happy to have a go on that.

Ah the others should be on hold in favor of this one?

Exactly. Other issues need deeplinks work as expected to test their proposal so this issue need to be solved in order to move forward with other issues.