Android - NetSuite - App freezes then crashes when connecting to NetSuite

[IuliiaHerets]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.0.58-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5188341
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team

Action Performed:

1. Login to the hybrid app with an account
2. Create a new workspace
3. Go to workspace settings > More features > Enable accounting
4. In the accountings page connect to NetSuite > Upgrade to control > Finish
5. Go through the flow of entering the credentials for connecting to NetSuite

Expected Result:

The workspace connects to NetSuite

Actual Result:

App freezes then crashes

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

0611_7.txt

Bug6656457_1730889881823.video_2024-11-06_13-44-00.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @srikarparsi

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @adelekennedy (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.

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

[adelekennedy]

@srikarparsi do you think this is a deployblocker? I Definitely think it's high priority but wonder if we can downgrade as it's only affecting Android users setting up an NS connection?

[srikarparsi]

Hey! Taking a look

[srikarparsi]

Checking if this is still reproducible since a lot of the crash errors got fixed by this revert

[srikarparsi]

Yeah, I think this was also fixed by this CP. I'm going to close this out since it's not reproducible on staging anymore.