-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD App#54614] Expensify Card - State is not auto populated in Add shipping details flow after adding address in Get physical card flow. #52488
Comments
Triggered auto assignment to @OfstadC ( |
It appears to be a backend bug. The frontend sends the state value to the backend, but the backend returns an empty string in private_personalDetails |
cc @mountiny |
Thanks @mountiny ❤️ |
no update yet |
same |
no update yet |
No update still |
No updates yet, lower priority |
Still no updates focusing on other issues, this is minor |
Same |
No updates |
low |
Actually putting this on hold for #54614 as it will be irrelevant after those changes I think |
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.61-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Precondition:
Expected Result:
In Step 11, state will be auto populated in address page because the rest of the address is added to relevant fields.
In Step 17, user should be able to proceed after manually entering state.
Actual Result:
In Step 11, state is not auto populated in address page, while the rest of the address is added to relevant fields.
In Step 17, user is unable to proceed after manually entering state.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6664039_1731515088843.bandicam_2024-11-14_00-23-25-931.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @mountinyThe text was updated successfully, but these errors were encountered: