-
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-03-11] [$500] Sign In - 'continue with the web app' link is not working on click #36145
Comments
Job added to Upwork: https://www.upwork.com/jobs/~018b1482288004dd72 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
Triggered auto assignment to @jliexpensify ( |
We think that this bug might be related to #wave9-collect-signup |
ProposalPlease re-state the problem that we are trying to solve in this issue.continue with the web app' link is not working on click What is the root cause of that problem?We navigate to
What changes do you think we should make in order to solve the problem?Update the What alternative solutions did you explore? (Optional)N/A |
@izarutskaya , the bug video hasn't been uploaded yet, can you please update it :) thanks |
Sorry, I added it again |
Do I need to apply through upwork? |
📣 @DevOpsacmeuniverse! 📣
|
HI |
📣 @kevalacme! 📣
|
Contributor details |
|
Contributor details |
|
ProposalPlease re-state the problem that we are trying to solve in this issue.The 'continue with the web app' text link doesn't do anything. What is the root cause of that problem?The 'continue with the web app' link navigates to HOME.
HOME is a bottom tab route screen and if the bottom tab action here is undefined, it returns early and does nothing. App/src/libs/Navigation/linkTo.ts Lines 203 to 210 in dafaf7f
The action will be undefined if the bottom tab screen we are targeting is the same topmost bottom tab screen. App/src/libs/Navigation/linkTo.ts Lines 95 to 111 in c3ae221
After we log in, the topmost bottom tab screen is HOME, so when we try to navigate to HOME, it does nothing. What changes do you think we should make in order to solve the problem?Instead of navigating to HOME, we can just simply call or dismissModal What alternative solutions did you explore? (Optional)Instead of early return if the bottom tab screen target is the same, we can change the action type to NAVIGATE.
but this will have the same effect as |
Asking Mitch here - https://expensify.slack.com/archives/C05NJ4SLBMF/p1707437575132939 |
@izarutskaya I understand that we had a SSO 🔥 earlier - can you re-test this and make sure the link still isn't working? I don't think this is related to the fire, but probably good to make sure! |
@abdulrahuman5196 how does @bernhardoj 's proposal look to you? |
@jliexpensify, @abdulrahuman5196 Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Hi, Will work on review today. |
Bump @abdulrahuman5196 , have you reviewed the comments? |
Reviewing now |
@bernhardoj 's proposal here #36145 (comment) looks good and works well. 🎀 👀 🎀 |
Triggered auto assignment to @nkuoch, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@nkuoch @jliexpensify @abdulrahuman5196 this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
📣 @abdulrahuman5196 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
PR is ready |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.46-2 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-03-11. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Doesn't have regression PR directly. Could be cause of common navigation changes.
Yes.
|
Payment Summary:
|
Paid and job closed. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.38.0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation:
Action Performed:
Expected Result:
User should be signed in to browser
Actual Result:
The link is not working
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6371750_1707397032754.Screen_Recording_2024-02-07_at_11.47.44_at_night.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: