If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Details
Following this slack convo: https://expensify.slack.com/archives/C03TQ48KC/p1635812089454700
Related GH issues:
We will be doing the following changes related to the address fields in the VBA flow:
- Always show all separate inputs for:
city, state, street + number + (apt number), zip code
- The input
street + number will keep its autocomplete behaviour.
- If the user selects a result, we will populate other fields. If the result is missing any part of the address (i.e. city), we will just ignore that part.
- The user will be allowed to manipulate and enter data manually in any of the address components (i.e. add the apt number to the
street + number input)
The following steps have to be consistently updated:
- Company information
- Personal information (requestor)
- Additional information (beneficial owners)
Expected Result:

Actual Result:


Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
- Web
- iOS
- Android
- Desktop App
- Mobile Web
Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Details
Following this slack convo: https://expensify.slack.com/archives/C03TQ48KC/p1635812089454700
Related GH issues:
We will be doing the following changes related to the address fields in the VBA flow:
city,state,street + number + (apt number),zip codestreet + numberwill keep its autocomplete behaviour.street + numberinput)The following steps have to be consistently updated:
Expected Result:
Actual Result:
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub