Skip to content

[HOLD for payment 2023-02-01] [$250] There's no back button at bank offline blocking view reported by @thesahindia  #12708

Closed

Description

@kavimuru

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


Action Performed:

  1. Disconnect the internet connection
  2. Navigate to settings > Workspaces
  3. Select a workspace
  4. Click on "connect bank account"

Expected Result:

There should be a back button

Actual Result:

There's no back button

Workaround:

unknown

Platform:

Where is this issue occurring?

  • Web
  • iOS
  • Android
  • Desktop App
  • Mobile Web

Version Number: 1.2.27-3

Reproducible in staging?: y

Reproducible in production?: y

Email or phone of affected tester (no customers):

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/201705335-a707a598-e65e-42cb-9b4e-6f2556c555a9.mov
Screenshot (99)

Expensify/Expensify Issue URL:

Issue reported by: @thesahindia

Slack conversation:
https://expensify.slack.com/archives/C049HHMV9SM/p1668369917906139

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 14, 2022
  2. melvin-bot commented on Nov 14, 2022

    @melvin-bot

    Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

  3. Puneet-here commented on Nov 14, 2022

    @Puneet-here
    Contributor

    Proposal

    We need to show the back button when the user is offline we can make the changes as suggested at ReimbursementAccountLoadingIndicator

             <HeaderWithCloseButton
                 title={props.translate('reimbursementAccountLoadingAnimation.oneMoment')}
                 onCloseButtonPress={Navigation.dismissModal}
    +            shouldShowBackButton={props.network.isOffline}
    +            onBackButtonPress={Navigation.goBack}
             />
             <FullPageOfflineBlockingView>
                 {props.isSubmittingVerificationsData ? (
    @@ -49,4 +53,7 @@ const ReimbursementAccountLoadingIndicator = props => (
     ReimbursementAccountLoadingIndicator.propTypes = propTypes;
     ReimbursementAccountLoadingIndicator.displayName = 'ReimbursementAccountLoadingIndicator';
     
    -export default withLocalize(ReimbursementAccountLoadingIndicator);
    +export default compose(
    +    withNetwork(),
    +    withLocalize,
    +)(ReimbursementAccountLoadingIndicator);
  4. melvin-bot commented on Nov 14, 2022

    @melvin-bot

    Looks like something related to react-navigation may have been mentioned in this issue discussion.

    As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

    Feel free to drop a note in #expensify-open-source with any questions.

  5. added
    ExternalAdded to denote the issue can be worked on by a contributor
    on Nov 15, 2022
  6. melvin-bot commented on Nov 15, 2022

    @melvin-bot

    Current assignee @dylanexpensify is eligible for the External assigner, not assigning anyone new.

  7. melvin-bot commented on Nov 15, 2022

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @eVoloshchak (External)

  8. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Nov 15, 2022
  9. melvin-bot commented on Nov 15, 2022

    @melvin-bot

    Triggered auto assignment to @AndrewGable (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

  10. changed the title [-]There's no back button at bank offline blocking view reported by @thesahindia [/-] [+][$250] There's no back button at bank offline blocking view reported by @thesahindia [/+] on Nov 15, 2022
  11. dylanexpensify commented on Nov 15, 2022

    @dylanexpensify
    Contributor
  12. 44 remaining items

  13. melvin-bot commented on Jan 25, 2023

    @melvin-bot

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

  14. melvin-bot commented on Jan 25, 2023

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 1.2.58-4 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 2023-02-01. 🎊

    After the hold period, please check if any of the following need payment for this issue, and if so check them off after paying:

    • External issue reporter
    • Contributor that fixed the issue
    • Contributor+ that helped on the issue and/or PR

    As a reminder, here are the bonuses/penalties that should be applied for any External issue:

    • Merged PR within 3 business days of assignment - 50% bonus
    • Merged PR more than 9 business days after assignment - 50% penalty
  15. melvin-bot commented on Jan 25, 2023

    @melvin-bot

    BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

    • [@nkuoch] The PR that introduced the bug has been identified. Link to the PR: N/A - Bug has always been there
    • [@nkuoch] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: N/A
    • [@nkuoch] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A - It was an improvement more than a bug
    • [@dylanexpensify] A regression test has been added or updated so that the same bug will not reach production again. Link to the GH issue for creating the test here:
  16. dylanexpensify commented on Feb 6, 2023

    @dylanexpensify
    Contributor

    Working on this today!

  17. dylanexpensify commented on Feb 8, 2023

    @dylanexpensify
    Contributor

    RT here

  18. thesahindia commented on Feb 9, 2023

    @thesahindia
    Member

    @dylanexpensify, this is eligible for reporting compensation. We will need an upwork job here.

  19. dylanexpensify commented on Feb 13, 2023

    @dylanexpensify
    Contributor

    Ah yes, will do now

  20. dylanexpensify commented on Feb 13, 2023

    @dylanexpensify
    Contributor

    job here, also invited you!

  21. thesahindia commented on Feb 13, 2023

    @thesahindia
    Member

    Applied, thanks!

  22. dylanexpensify commented on Feb 13, 2023

    @dylanexpensify
    Contributor

    offer sent!

  23. thesahindia commented on Feb 13, 2023

    @thesahindia
    Member

    @dylanexpensify, accepted!

  24. dylanexpensify commented on Feb 13, 2023

    @dylanexpensify
    Contributor

    paid! Closing this out @nkuoch reopen if something is missing!

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.InternalRequires API changes or must be handled by Expensify staffWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions