Skip to content
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 2023-12-29] [HOLD for payment 2023-12-28] Sign up - App crashes when signing up with a new account via magic link #33354

Closed
1 of 6 tasks
kbecciv opened this issue Dec 20, 2023 · 10 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering Weekly KSv2

Comments

@kbecciv
Copy link

kbecciv commented Dec 20, 2023

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: v1.4.14-2
Reproducible in staging?: y
Reproducible in production?: n
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:

Action Performed:

Precondition: App must be freshly installed, or clear app data before running the steps below.

  1. Launch New Expensify app.
  2. Enter a new email account.
  3. On magic code page, navigate to email and tap on the magic link.

Expected Result:

App does not crash.

Actual Result:

App crashes.

Workaround:

Unknown

Platforms:

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

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6321189_1703076281038.Screen_Recording_20231220_193139_One_UI_Home__1_.mp4

View all open jobs on GitHub

@kbecciv kbecciv added the DeployBlockerCash This issue or pull request should block deployment label Dec 20, 2023
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

Copy link

melvin-bot bot commented Dec 20, 2023

Triggered auto assignment to @puneetlath (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@kbecciv
Copy link
Author

kbecciv commented Dec 20, 2023

Not reproducible in production

Screen_Recording_20231220_193915_New.Expensify.mp4

@ikevin127
Copy link
Contributor

I can reproduce it with 100% success rate on local with latest main performing the following actions:

Precondition: App must be killed / closed (not opened in background) before running the steps below.

  1. Launch New Expensify app.
  2. Enter email account and tap Continue.
  3. While on magic code page, navigate to your email and tap on the magic link.

Issue seems to be caused by the following line of code:

const topRouteName = rootState.routes.at(-1)?.name;

because the rootState.routes is undefined when attempting deep-link login first time the app is opened.

iOS: Native - Screenshot Screenshot 2023-12-20 at 15 17 24

The issue does not occur on subsequent trials if the app is not killed / closed and I think this is because subsequently the rootState.routes is not undefined anymore.

@mkhutornyi
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

Sign up - App crashes when signing up with a new account via magic link

What is the root cause of that problem?

This is regression from #32473
image

What changes do you think we should make in order to solve the problem?

Like old code, optional chaining should be added

@WojtekBoman
Copy link
Contributor

Hello! Thank you for finding the cause of the problem :) I will add a fix in this PR which is also related to LHP #33359

@mkhutornyi
Copy link
Contributor

The crash fix needs to be CPed. I don't think #33359 should be necessarily CPed.
Can we fix separately?

@jasperhuangg jasperhuangg added Daily KSv2 and removed DeployBlockerCash This issue or pull request should block deployment Hourly KSv2 labels Dec 21, 2023
@jasperhuangg
Copy link
Contributor

Closing, fix was CP'd

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels Dec 21, 2023
@melvin-bot melvin-bot bot changed the title Sign up - App crashes when signing up with a new account via magic link [HOLD for payment 2023-12-28] Sign up - App crashes when signing up with a new account via magic link Dec 21, 2023
Copy link

melvin-bot bot commented Dec 21, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.14-6 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 2023-12-28. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Weekly KSv2 labels Dec 22, 2023
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2023-12-28] Sign up - App crashes when signing up with a new account via magic link [HOLD for payment 2023-12-29] [HOLD for payment 2023-12-28] Sign up - App crashes when signing up with a new account via magic link Dec 22, 2023
Copy link

melvin-bot bot commented Dec 22, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.15-5 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 2023-12-29. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • External issue reporter
  • Contributor that fixed the issue
  • Contributor+ that helped on the issue and/or PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Engineering Weekly KSv2
Projects
None yet
Development

No branches or pull requests

6 participants