Skip to content

iOS- Notification - App crashes when tapping on the second notification #61324

Closed

Description

@nlemma

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.1.39-2
Reproducible in staging?: Yes
Reproducible in production?: Unable to check - new feature testing
If this was caught during regression testing, add the test name, ID and link from TestRail: #61125
Email or phone of affected tester (no customers): htad26+jdjfdbdbfxc@gmail.com
Issue reported by: Applause Internal Team
Device used: iPhone 13/iOS 18.4.1
App Component: Notifications

Action Performed:

Precondition: Notification is enabled for the app

  1. Navigate to the iOS app
  2. Sign in with a new Gmail account
  3. For the onboarding modal, select "Manage my team's expenses", > Select 11-50
  4. Choose Sage Intacct as an accounting option
  5. Here notice that the first notification appears
  6. When the second notification appears, quickly tap on it

Expected Result:

The user is navigated to concierge chat

Actual Result:

The app crashes

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6819406_1746179847432.video_2025-05-02_12-55-17.mp4

Bug6819406_1746188401795!logs-2025-05-02_12_17_17.395.txt

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on May 2, 2025
  2. melvin-bot commented on May 2, 2025

    @melvin-bot

    Triggered auto assignment to @trjExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  3. melvin-bot commented on May 2, 2025

    @melvin-bot

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

  4. melvin-bot commented on May 2, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on May 2, 2025

    @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.
  6. nlemma commented on May 2, 2025

    @nlemma
    Author

    @trjExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

  7. trjExpensify commented on May 2, 2025

    @trjExpensify
    Contributor

    I can repro this on iOS reliably, @dangrous. Even using a private domain account 👍

  8. dangrous commented on May 2, 2025

    @dangrous
    Contributor

    Looking into it!

  9. dangrous commented on May 2, 2025

    @dangrous
    Contributor

    oh arg since it's notifications it's going to be trickier since I have to build it on my physical phone. Stay tuned...

  10. dangrous commented on May 2, 2025

    @dangrous
    Contributor

    Caused or at least revealed by #61125 which gives us a starting point. My initial guess is it's some problem with trying to switch to Old Dot while New Dot is still loading.

  11. ChavdaSachin commented on May 2, 2025

    @ChavdaSachin
    Contributor

    This PR could be relevant #60047

  12. parasharrajat commented on May 2, 2025

    @parasharrajat
    Member

    #61125 could not cause this as we didn't change navigational logic at all.

  13. dangrous commented on May 2, 2025

    @dangrous
    Contributor

    @parasharrajat yeah I don't think it caused it, but it may be a new scenario for an existing bug that wasn't accessible until we kept users in New Dot.

    @arosiclair do you have any thoughts on the notification behavior here? You know way more about them than I do.

    Going to keep working on replicating this locally though my physical phone is not cooperating

  14. dangrous commented on May 2, 2025

    @dangrous
    Contributor

    okay got notifications working on dev on staging but it only crashed for me once, the other ones are working. Will keep trying

  15. dangrous commented on May 2, 2025

    @dangrous
    Contributor
  16. dangrous commented on May 5, 2025

    @dangrous
    Contributor

    Discussing in Slack, awaiting feedback from original internal team as to whether we should revert or not.

  17. dangrous commented on May 5, 2025

    @dangrous
    Contributor

    Fixed by revert - #61388

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions