Skip to content

[HOLD for payment 2025-01-02] [$250] Android - Crash when kill the app and reopen it #50463

Closed

Description

@lanitochka17

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.46-1
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): gocemate+a2536@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Install the New dot app
  2. Open android app
  3. Login with new gmail account
  4. Complete the onboarding modal
  5. Kill the app
  6. Open the app

Expected Result:

App should open

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
Bug6628394_1728395962594.Recording__4245.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021843775413325774813
  • Upwork Job ID: 1843775413325774813
  • Last Price Increase: 2024-11-19
  • Automatic offers:
    • DylanDylann | Reviewer | 105060601
    • shubham1206agra | Contributor | 105341816
Issue OwnerCurrent Issue Owner: @shubham1206agra

Activity

  1. melvin-bot commented on Oct 8, 2024

    @melvin-bot

    Triggered auto assignment to @srikarparsi (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  2. github-actions commented on Oct 8, 2024

    @github-actions
    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.
  3. srikarparsi commented on Oct 8, 2024

    @srikarparsi
    Contributor

    Not able to reproduce on my physical ios device with a new account. Going to try on android emulator.

  4. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    There's been an emerging crash in firebase that looks like it might be related here
    com.expensify.chat_issue_4f8a216f0a769e684d009b28ef9bd7d4_crash_session_6705473302F5000179E748FD60E92734_DNE_0_v2_stacktrace.txt

    SurfaceMountingManager.getViewState

    Appears to be present in a few different versions, so maybe not a deploy blocker

  5. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    Potentially related: react/react-native#38743

  6. thienlnam commented on Oct 8, 2024

    @thienlnam
    Contributor

    @kirillzyusko Do you think this #37891 would address this crash as well?

  7. changed the title [-]Android - Crash when kill the app and reopen it[/-] [+][HOLD #50482] Android - Crash when kill the app and reopen it[/+] on Oct 8, 2024
  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Oct 8, 2024
  9. srikarparsi commented on Oct 8, 2024

    @srikarparsi
    Contributor
  10. 99 remaining items

  11. melvin-bot commented on Dec 26, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Dec 26, 2024

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.78-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 2025-01-02. 🎊

    For reference, here are some details about the assignees on this issue:

  13. melvin-bot commented on Dec 26, 2024

    @melvin-bot

    @shubham1206agra @kadiealexander @shubham1206agra The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. shubham1206agra commented on Jan 5, 2025

    @shubham1206agra
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 1a. Result of the original design (eg. a case wasn't considered)
    • 1b. Mistake during implementation
    • 1c. Backend bug
    • 1z. Other: RN bug

    Where bug was reported:

    • 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
    • 2b. Reported on staging (eg. found during regression or PR testing)
    • 2d. Reported on a PR
    • 2z. Other:

    Who reported the bug:

    • 3a. Expensify user
    • 3b. Expensify employee
    • 3c. Contributor
    • 3d. QA
    • 3z. Other:
    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: NA since the mistake is in RN implementation, not App implementation.

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: Not Required

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue:

    Regression Test Proposal

    Test:

    No test is needed since it was a deploy blocker, and the test is already present in Test Rail.

    Do we agree 👍 or 👎

  15. kadiealexander commented on Jan 6, 2025

    @kadiealexander
    Contributor

    @shubham1206agra could you please accept the Upwork contract?

  16. melvin-bot commented on Jan 9, 2025

    @melvin-bot

    @j-piasecki, @srikarparsi, @shubham1206agra, @kadiealexander Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  17. shubham1206agra commented on Jan 9, 2025

    @shubham1206agra
    Contributor

    @kadiealexander Offer accepted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions