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
Android - Field error triggered for company type even after user select the company type option #67015
Version Number: 9.1.85-2 Reproducible in staging?: Y Reproducible in production?: Unable to validate in Prod 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):applausetester+ck723253@applause.expensifail.com Issue reported by: Applause - Internal Team
Action Performed:
Launch Hybrid app on Android device
Sign in with new account & create a workspace
Go to Workspaces >> Workflows >> Connect BA
Go through the Plaid flow selecting Regions bank
Go through Personal info step
On the company info step, select any valid company type option (LLC, Corp, Sole proprietorship, Cooperative, Partnership, Other)
Expected Result:
Error message "This field is required" should not be displayed after user selects company type option.
The error should be thrown only when user select "Next" button without selecting the company type
Actual Result:
Field error "This field is required" triggered for company type even after user select the company type option
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
Android: App
Android: mWeb Chrome
iOS: App
iOS: mWeb Safari
iOS: mWeb Chrome
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6896791_1753304600762.az_recorder_20250723_162020.mp4
👋 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.
Activity
github-actions commentedon Jul 23, 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:
melvin-bot commentedon Jul 23, 2025
Triggered auto assignment to @OfstadC (
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 Jul 23, 2025
Triggered auto assignment to @neil-marcellini (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 23, 2025
💬 A slack conversation has been started in #expensify-open-source
4 remaining items
cristipaval commentedon Jul 24, 2025
I can also confirm this is not reproducible with 9.1.84-4 (the current version in production)
cristipaval commentedon Jul 24, 2025
I'm now testing here to see if this is the culprit
cristipaval commentedon Jul 24, 2025
confirming that the revert fixes it