Skip to content

[Due for payment 2025-08-20] Wallet - All the information user entered offline disappear #67256

Closed

Description

@izarutskaya

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 9.1.86-3
Reproducible in staging?: Yes
Reproducible in production?: Unable to validate in Production as it's Bank account flow
If this was caught during regression testing, add the test name, ID and link from TestRail: #65081
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal team
Slack conversation (hyperlinked to channel name):

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Go to the wallet page in an account with no default country set (no prior bank account, addresses, etc).
  3. Click Add bank account and land on the country selector> Select a country> Go offline>Verify you see the full page pattern D offline blocking screen.
  4. Go online>Verify you see the country selector with your selector prior to going offline> Click Next to land on the bank account details page
  5. Go offline > Verify the currency row is disabled (since this can’t be edited offline; Verify the other fields on the page can be edited offline;
    Verify the Next button is not disabled and has normal opacity.
  6. Go online.> Verify the Currency row is no longer disabled.
  7. Complete any remaining fields on the page.
  8. Click Next to land on the account type selector> Verify you can make adjustments to this page offline; Verify the Next button has normal opacity and is not disabled.
  9. Click Next to land on the bank details page >Verify you can make adjustments to every field on this page (google maps API autofill of address won’t work offline).
  10. Verify the Next button has normal opacity and is not disabled.
  11. Complete all fields on the page.
  12. Click Next to land on the account holder details page> Verify you can make adjustments to every field on this page (google maps API autofill of address won’t work offline> Verify the Next button has normal opacity and is not disabled.
  13. Complete all fields on the page.
  14. Click Next to land on the confirmation page> Verify Country and Currency rows are disabled (since they can’t be edited offline); Verify Confirm is disabled and has higher opacity; Verify all other rows on the page are enabled, and their field input changeable offline.
  15. Click < several times until you get back to the country selector>Verify you now can’t proceed any further than this page while offline.
  16. Go back online.
  17. Click through the rest of the form you complete offline, stopping before the confirmation page> Verify all the info you entered offline remains.

Expected Result:

All the info you entered offline remains when user go back on-line.

Actual Result:

User is losing all information after go back On line.

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

PR_65081_6_Offline.-.Mid-deposit.account.flow.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @stephanieelliott

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jul 28, 2025
  2. melvin-bot commented on Jul 28, 2025

    @melvin-bot

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

  3. github-actions commented on Jul 28, 2025

    @github-actions
    Contributor

    👋 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.
  4. melvin-bot commented on Jul 28, 2025

    @melvin-bot

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

  5. melvin-bot commented on Jul 28, 2025

    @melvin-bot

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

  6. grgia commented on Jul 28, 2025

    @grgia
    Contributor

    Caused by #65081

    I'm demoting this as a blocker and assigning cc @pasyukevich @DylanDylann

  7. 46 remaining items

  8. changed the title [-]Wallet - All the information user entered offline disappear[/-] [+][Due for payment 2025-08-20] Wallet - All the information user entered offline disappear[/+] on Aug 13, 2025
  9. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  10. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.93-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2025-08-20. 🎊

    For reference, here are some details about the assignees on this issue:

  11. melvin-bot commented on Aug 13, 2025

    @melvin-bot

    @DylanDylann @stephanieelliott The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  12. melvin-bot commented on Aug 20, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    • Contributor: @pasyukevich is from an agency-contributor and not due payment
    • Reviewer: @DylanDylann owed $250 via NewDot

    BugZero Checklist (@stephanieelliott)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
    • I have verified the PR was not reverted
    • I have applied any discounts due to bugs/regressions introduced by this PR
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. stephanieelliott commented on Aug 21, 2025

    @stephanieelliott
    Contributor

    Payment Summary

    Contributor: @pasyukevich no payment due
    Contributor+: @DylanDylann due $250 via NewDot

  14. garrettmknight commented on Oct 29, 2025

    @garrettmknight
    Contributor

    $250 approved for @DylanDylann

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions