QBO - The app crashes after connecting to QBO and tapping on a setting a few times

[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.10-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: https://expensify.testrail.io/index.php?/tests/view/4751067&group_by=cases:section_id&group_id=309135&group_order=asc
Issue reported by: Applause - Internal Team

Action Performed:

1. Open the app
2. Log in with a new Gmail account
3. Create a workspace
4. Enable "Accounting" from the workspace settings
5. Navigate to Accounting
6. Connect to QBO
7. Tap on any setting button under QBO after it has finished syncing

Expected Result:

I should be able to navigate to the settings page without crashing the app

Actual Result:

The app crashes after connecting to QBO and tapping on a setting a few times

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

Bug6549245_1721643154443.HCYE6048.mp4

1.log
2.log

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~011d5086ea67aef1e7
• Upwork Job ID: 1815631807021214555
• Last Price Increase: 2024-07-23

Issue Owner

Current Issue Owner: @paultsimura

[melvin-bot]

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

[github-actions]

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

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[mountiny]

Maybe its related to this crash which is the only one seen in the firebase
com.chat.expensify.chat_issue_ee1256448fb6b0ac22a0e9a88c62f18e_crash_session_dbb68c266fb6498e979aaa2c340f54a9_DNE_0_v2_stacktrace.txt
com.chat.expensify.chat_issue_ee1256448fb6b0ac22a0e9a88c62f18e_crash_session_dbb68c266fb6498e979aaa2c340f54a9_DNE_0_v2.log

[mountiny]

Discussing here

[mountiny]

This is apparently still happening even after the CP :/

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~011d5086ea67aef1e7

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @paultsimura (External)

[mountiny]

Seems like the crash is resolved though and the other issues observed.

This was apparently seen again and in android the App did not crash but became unresponsive

Screenrecorder-2024-07-23-00-39-04-566.mp4

[mountiny]

I have just gone through the flow on the latest staging, and it worked well, I demoting to further investigate. Here are the logs and cpu traces from the long flow, i took a while to find the login details

logs-2024-07-23 07_39_59.998.txt
App_Info_9.0.10-2 2.json
Profile_trace_for_9.0.10-2.cpuprofile 2.zip

Here is the video

RPReplay_Final1721720409.mp4

[kavimuru]

No crash occurs now. stuck in 'Waiting for imported data to load". Tester has to revisit the page.

log_qbo.log

77da.mp4

App_Info_9.0.11-0.json

Screenrecorder-2024-07-23-16-46-44-418.mp4

logs-2024-07-23 13_51_03.635.txt

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.11-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Backport a fix for react-native-gesture-handler #45918

If no regressions arise, payment will be issued on 2024-08-01. 🎊

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

• @paultsimura requires payment (Needs manual offer from BZ)

[melvin-bot]

Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

[melvin-bot]

Payment Summary

Upwork Job

• ROLE: @paultsimura paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@mallenexpensify)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1815631807021214555/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[melvin-bot]

@nkuoch, @paultsimura, @mallenexpensify, @mountiny Huh... This is 4 days overdue. Who can take care of this?

[melvin-bot]

@nkuoch, @paultsimura, @mallenexpensify, @mountiny Still overdue 6 days?! Let's take care of this!

[mountiny]

Probably nothing else to do here really, seems like a weird one off issue