-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$50] Onboarding - Deeplink in concierge chat doesn't navigate to the correct screen within the app #50648
Comments
Triggered auto assignment to @lakchote ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Not reproducible in dev. I don't think this should be a blocker since when the deploy checklist hits production, the deeplink URL in Concierge chat will be correct. |
Job added to Upwork: https://www.upwork.com/jobs/~021844750386942511406 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.The app generates a link with a production URL and redirects to production What is the root cause of that problem?In here, we are checking has the same origin, it mean in staging we can not open link with the origin Line 155 in e4969b2
Lines 174 to 181 in e4969b2
What changes do you think we should make in order to solve the problem?We can remove What alternative solutions did you explore? (Optional)Screen.Recording.2024-10-12.at.03.51.20.mov |
|
Please re-state the problem that we are trying to solve in this issue.) What is the root cause of that problem? This is a BE problem, the content of this specific automated message is from the backend where it's constructed with an explicit href for the anchor tag that equals to the production url which is new.expensify.com instead of the staging or the development (It happens on both). The Front-End apps are just displaying what they're getting (which make sense as these messages should be generated on the backend and displayed as is) and for this message we are getting the production url. The server is not taking into account the origin of the https request instead it's treating all users as if they're coming from production, maybe even this specific message is fixed for all users. What changes do you think we should make in order to solve the problem? What alternative solutions did you explore? (Optional) One final note to mention is that after this message, neither the user nor the Concierge chat can regenerate the same href style (Imbedding the url within a text) for example writing "GOOGLE" but enabling a redirection to "www.google.com" when pressing the word. |
📣 @saraSwiti001! 📣
|
We should not introduce staging specific logic. @nkdengineer could you please answer this question from @situchan:
|
@nkdengineer no, it's not. That PR just moved logic from here |
No viable solution yet |
@lakchote Since the report link in the start free trial is the production link, I have two options with two behavior
Line 190 in e4969b2
App/src/libs/ReportActionsUtils.ts Line 752 in 0b547fc
|
Since it's a deeplink, redirecting to the correct room without opening a tab is expected. @situchan what do you think of option #2 from @nkdengineer? |
Option 2 sounds good to me |
I like option #2 too, @nkdengineer let's go with that. |
📣 @situchan 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @nkdengineer 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@lakchote This will require the BE change that will change the When it's done I will create an FE PR to update App/src/libs/ReportActionsUtils.ts Lines 737 to 740 in 0b547fc
|
Upwork job price has been updated to $50 |
I've discussed about the issue internally. Given that's an automated message in concierge for a free trial, it'd really only affect applause and internal employees (even then it'd be an edge case), We've decided to not fix that because it only affects staging. Though you should be compensated for the work done so far @nkdengineer @situchan, that's why I'm proposing a $50 payment for each of you. Assigning a BZ member to issue payment, and then I'll close the issue. |
Triggered auto assignment to @trjExpensify ( |
@trjExpensify please see my comment just above, thanks! |
Cool, payment summary as follows:
Let me know when you have accepted the pending offers that have already been sent. Then I'll adjust and settle. |
@trjExpensify, @lakchote, @situchan, @nkdengineer Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@situchan, paid. @nkdengineer, waiting for you to accept the offer. |
^ @nkdengineer did you accept the offer? |
@lakchote I just did, thanks |
Paid, closing! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.48-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): htad26+dfhjkdsghg@gmail.com
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The app should generate a link with a staging URL and should redirect to the correct screen within the app
Actual Result:
The app generates a link with a production URL and redirects to production
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6631539_1728628103931.2024-10-11_07_12_08.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @situchanThe text was updated successfully, but these errors were encountered: