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
[Due for payment 2026-06-09] [$250] [Exploratory] 84634 - Wallet - International Bank can be saved with wrong credentials failing if autocorrected #84811
Version Number: 9.3.34-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176692/test-cases/41236749 Email or phone of affected tester (no customers):gatantm+636a@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: iPhone 12 mini, iOS 16.7 App Component: Other
Action Performed:
Launch expensify and login with any account
Tap on Account > Wallet
Tap on Add bank account > Get reimbursed
Select India as the country
Add an ISFC code
For account number type something that will be autocorrected from IOS (e.g Whats)
Tap next and follow the flow until reaching he confirm page and confirm
Expected Result:
The word is not autocorrected to something that is invalid and the app doesn't allow it to be saved
Actual Result:
On specific strings the iOS will auto correct them even if leaving the screen with the on screen validation be skipped and then the bank can't saved although the typed word is valid. The user won't easily understand why the validation fails
The bank account input fields (account number, IFSC/routing code, SWIFT, etc.) in the international deposit account flow are rendered as TextInput components with iOS autocorrect enabled by default. The native BaseTextInput defaults to autoCorrect = true (index.native.tsx:65), and none of the bank detail form pages override this.
Additionally, the Confirmation page only validates acceptTerms — it does not re-validate bank field values before sending them to the API. So if autocorrect modifies a value after step-level validation passed, the corrupted value reaches the API unchecked.
What changes do you think we should make in order to solve the problem?
Add autoCorrect={false} and spellCheck={false} to all TextInput fields in the bank account detail forms listed above. These fields accept structured data (account numbers, IFSC codes, SWIFT codes) where autocorrect is always harmful.
This should be applied to the InputWrapper components in all three affected files, specifically for fields that render as TextInput (not ValuePicker).
What alternative solutions did you explore? (Optional)
An alternative would be to re-validate all bank field values on the Confirmation page before submission. However, disabling autocorrect on structured financial input fields is the more direct and appropriate fix — autocorrect should never apply to bank account numbers and routing codes regardless of downstream validation.
Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.
changed the title [-][Exploratory] 84634 - Wallet - International Bank can be saved with wrong credentials failing if autocorrected[/-][+][$250] [Exploratory] 84634 - Wallet - International Bank can be saved with wrong credentials failing if autocorrected[/+]on Apr 13, 2026
Activity
MelvinBot commentedon Apr 13, 2026
Proposal
What is the root cause of that problem?
The bank account input fields (account number, IFSC/routing code, SWIFT, etc.) in the international deposit account flow are rendered as
TextInputcomponents with iOS autocorrect enabled by default. The nativeBaseTextInputdefaults toautoCorrect = true(index.native.tsx:65), and none of the bank detail form pages override this.The affected pages are:
BankAccountDetails.tsx(personal wallet flow)BankInformation.tsxNonUSD/BankInfo/subSteps/BankAccountDetails.tsx(workspace flow)Additionally, the Confirmation page only validates
acceptTerms— it does not re-validate bank field values before sending them to the API. So if autocorrect modifies a value after step-level validation passed, the corrupted value reaches the API unchecked.What changes do you think we should make in order to solve the problem?
Add
autoCorrect={false}andspellCheck={false}to allTextInputfields in the bank account detail forms listed above. These fields accept structured data (account numbers, IFSC codes, SWIFT codes) where autocorrect is always harmful.This should be applied to the
InputWrappercomponents in all three affected files, specifically for fields that render asTextInput(notValuePicker).What alternative solutions did you explore? (Optional)
An alternative would be to re-validate all bank field values on the Confirmation page before submission. However, disabling autocorrect on structured financial input fields is the more direct and appropriate fix — autocorrect should never apply to bank account numbers and routing codes regardless of downstream validation.
Next Steps for Contributor+ team: Reply with
@MelvinBot implement thisto create a draft PR,@MelvinBot <your feedback>to refine this analysis, or explain why you are rejecting Melvin's proposal.melvin-bot commentedon Apr 13, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @truph01 (
External)[-][Exploratory] 84634 - Wallet - International Bank can be saved with wrong credentials failing if autocorrected[/-][+][$250] [Exploratory] 84634 - Wallet - International Bank can be saved with wrong credentials failing if autocorrected[/+]46 remaining items
melvin-bot commentedon Jun 8, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Jun 8, 2026
Payment Summary
Upwork Job
BugZero Checklist (@mallenexpensify)
melvin-bot commentedon Jun 11, 2026
@mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Jun 17, 2026
@mallenexpensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
mallenexpensify commentedon Jun 17, 2026
Payment Summary
Contributor+: @truph01 due $250 via NewDot
garrettmknight commentedon Aug 10, 2026
$250 approved for @truph01