-
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
[HOLD for payment 2024-06-13] [$250] [Guided Setup] Redirect where user was when they try to deeplink to the onboarding flow after completion #40876
Comments
Triggered auto assignment to @flodnv ( |
👋 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:
|
We think that this bug might be related to #wave-collect - Release 1 |
Taking over |
I think we discussed before if we should even allow the deeplink once user completed the flow @trjExpensify Nevertheless this is not a blocker as its minor ui bug |
I don't recall that, but it kinda' makes sense. If they've completed onboarding and in-product natively we don't show it again -- then getting there via deeplink shouldn't work either. |
Job added to Upwork: https://www.upwork.com/jobs/~01a5d3f767fe2611e7 |
Updated the instructions |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @c3024 ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Do not allow user repeat the onboarding steps when already completed the onboarding steps What is the root cause of that problem?New feature What changes do you think we should make in order to solve the problem?Backend sends
What alternative solutions did you explore? (Optional)n/a |
@mountiny PR is submitted. |
Looks like we're ready for a re-review here, @c3024. Thanks! |
This issue has not been updated in over 15 days. @skyweb331, @mountiny, @c3024 eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-13. 🎊 For reference, here are some details about the assignees on this issue:
|
Issue is ready for payment but no BZ is assigned. @joekaufmanexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
We need to pay:
|
@skyweb331 please share your upwork profile here so we can hire you |
@c3024 $250 sent and contract ended! |
@joekaufmanexpensify My profile link is https://www.upwork.com/freelancers/~019e5171478d2a22f7 |
TY! |
OG upwork job closed, so opened a new one: https://www.upwork.com/jobs/~013da32781154e6433 |
@skyweb331 offer sent for $250! |
@joekaufmanexpensify Thank you. Just accepted it. |
@skyweb331 $250 sent and contract ended! |
Upwork job closed. |
All set, thanks everyone! |
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: 1.4.65-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Issue found when executing PR: #40667
Action Performed:
Expected Result:
When the user already completed the guided setup flow, we should make sure we re-navigate them to the main page after they attempt to deeplink to the flow
Actual Result:
Users can go through the onboarding flow as many times as they want
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6460070_1713954299071.Screen_Recording_20240424_131955_New_Expensify.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: