-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[$500] [MEDIUM] Referral - Referral link is incomplete and missing contact details #32292
Comments
Triggered auto assignment to @conorpendergrast ( |
Job added to Upwork: https://www.upwork.com/jobs/~01cdb9a4da6bb420f6 |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ntdiary ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Referral link is showing empty email address when we generate referral link What is the root cause of that problem?On the referral page src/pages/ReferralDetailsPage.js Page when we are generating the referral url using the App/src/pages/ReferralDetailsPage.js Lines 57 to 59 in 56a368b
we are using the account.primaryLogin as a email address and sometimes (when a single email added as a contact method) we has empty primaryLogin valueApp/src/pages/ReferralDetailsPage.js Line 95 in 56a368b
What changes do you think we should make in order to solve the problem?Instead of the App/src/pages/ReferralDetailsPage.js Line 95 in 56a368b
urlToCopy={generateReferralURL(account.primaryLogin || session.email)}
What alternative solutions did you explore? (Optional)N/A |
ProposalPlease re-state the problem that we are trying to solve in this issue.The referral link is incomplete. The link is missing contact details What is the root cause of that problem?
We decided to fix in the back-end but due to low capacity, we did not fix it there. So in here, the primaryLogin is empty, causing the issue
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)We can consider removing the use of We cannot just fix it in the one place of |
ProposalPlease re-state the problem that we are trying to solve in this issue.The email details is not being populated to the copied shareable url for users that recently joined the app What is the root cause of that problem?I don't think there's a need to fix on the service side, this should be addressed on the FE app. The root cause lies on the App/src/pages/ReferralDetailsPage.js Lines 57 to 59 in cc4add5
And how is being called below with the primaryLogin, so it's assuming it's not empty: App/src/pages/ReferralDetailsPage.js Lines 92 to 95 in cc4add5
What changes do you think we should make in order to solve the problem?We should provide the credentials stored on Onyx, these hold the credentials the new user just entered to join the app, and on top of that, we should validate whether the What alternative solutions did you explore? (Optional)We could retrieve a user's session email through Onyx as well Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
Are there more specific reproduction steps that you were able to work out in developing your proposals @jayeshmangwani, @tienifr or @chiItepin? I haven't been able to reproduce through the steps above, but based on @tienifr details it seems like it might be:
Is that correct? |
@conorpendergrast Yes, that's exactly right, it only happens for recently created accounts. This explains why the "credentials" entity does have the "login" set in the onyx store |
@jayeshmangwani's proposal looks good to me. |
Triggered auto assignment to @tgolen, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@situchan Actually we decided to fix in the back-end but due to low capacity, we did not fix it there but use the front-end fix as a workaround instead. Front-end fix is not fixing the root cause so I think we should fix in back-end here. cc @tgolen |
Maybe @roryabraham has better context |
Oof, that's a long issue. It would be great if you had a TLDR @roryabraham. |
@tgolen, @conorpendergrast Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
PR ready for review #36556. |
Triggered auto assignment to @miljakljajic ( |
@miljakljajic, @roryabraham, @situchan, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@miljakljajic, @roryabraham, @situchan, @tienifr 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@miljakljajic PR was deployed to production 5 days ago. Please add |
@miljakljajic, @roryabraham, @situchan, @tienifr 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it! |
@miljakljajic, @roryabraham, @situchan, @tienifr 10 days overdue. Is anyone even seeing these? Hello? |
looks like the PR just wasn't linked correctly or our automation wasn't working. The PR has been on prod for 2 weeks with no regressions, so we can pay it out ASAP. |
@miljakljajic should be $500 each to @tienifr (C) and @situchan (C+) |
@miljakljajic, @roryabraham, @situchan, @tienifr Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@miljakljajic Could you proceed with this? Thanks |
@miljakljajic, @roryabraham, @situchan, @tienifr Still overdue 6 days?! Let's take care of this! |
@miljakljajic Here’s my UW profile: https://www.upwork.com/freelancers/~01991fd5e5c11ef3ba Thanks! |
Extended the contract to you too @tienifr |
@miljakljajic I’ve accepted the offer 🙏 |
Both contracts have now been paid! |
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.6.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
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #31827
Action Performed:
Expected Result:
The referral link is complete
Actual Result:
The referral link is incomplete. The link is missing contact details
This issue happens for some accounts but not all
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6296290_1701365730750.20231201_013259.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @miljakljajicThe text was updated successfully, but these errors were encountered: