You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
iOS- Notification - App crashes when tapping on the second notification #61324
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
Navigate to the iOS app
Sign in with a new Gmail account
For the onboarding modal, select "Manage my team's expenses", > Select 11-50
Choose Sage Intacct as an accounting option
Here notice that the first notification appears
When the second notification appears, quickly tap on it
👋 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:
Identify the pull request that introduced this issue and revert it.
@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.
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.
@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
Activity
melvin-bot commentedon May 2, 2025
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.melvin-bot commentedon May 2, 2025
Triggered auto assignment to @dangrous (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 2, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 2, 2025
👋 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:
nlemma commentedon May 2, 2025
@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.
trjExpensify commentedon May 2, 2025
I can repro this on iOS reliably, @dangrous. Even using a private domain account 👍
dangrous commentedon May 2, 2025
Looking into it!
dangrous commentedon May 2, 2025
oh arg since it's notifications it's going to be trickier since I have to build it on my physical phone. Stay tuned...
dangrous commentedon May 2, 2025
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.
ChavdaSachin commentedon May 2, 2025
This PR could be relevant #60047
parasharrajat commentedon May 2, 2025
#61125 could not cause this as we didn't change navigational logic at all.
dangrous commentedon May 2, 2025
@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
dangrous commentedon May 2, 2025
okay got notifications working on dev on
stagingbut it only crashed for me once, the other ones are working. Will keep tryingdangrous commentedon May 2, 2025
Stack Trace here - https://expensify.slack.com/archives/C01GTK53T8Q/p1746214053355919?thread_ts=1746189174.063199&cid=C01GTK53T8Q
Something to do with Live Markdown
dangrous commentedon May 5, 2025
Discussing in Slack, awaiting feedback from original internal team as to whether we should revert or not.
dangrous commentedon May 5, 2025
Fixed by revert - #61388