Skip to content
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 for payment 2023-05-22] Payments - Paypal.me account isn't "strikethrough'ed" in App after go offline and deleted #18459

Closed
2 of 6 tasks
kbecciv opened this issue May 4, 2023 · 20 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Internal Requires API changes or must be handled by Expensify staff

Comments

@kbecciv
Copy link

kbecciv commented May 4, 2023

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


Issue found when executing PR #17903

Action Performed:

  1. Open the App
  2. Sign in
  3. Go to your Settings -> Payments and add a Paypal.me account
  4. Go offline
  5. Delete that Paypal.me account
  6. Make sure that Paypal.me account still shows up but as grayed out and "strikethrough'ed"

Expected Result:

Paypal.me account is"strikethrough'ed" in all environments.

Actual Result:

Paypal.me account isn't "strikethrough'ed" in Android/iOS App

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: 1.3.10.2

Reproducible in staging?: Yes

Reproducible in production?: No

If this was caught during regression testing, add the test name, ID and link from TestRail:

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6043215_Screen_Recording_20230505_003421_New_Expensify.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~016feb202f5cafece9
  • Upwork Job ID: 1655605898197176320
  • Last Price Increase: 2023-05-08
@kbecciv kbecciv added Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels May 4, 2023
@melvin-bot
Copy link

melvin-bot bot commented May 4, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented May 4, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@jayeshmangwani
Copy link
Contributor

Proposal

Please re-state the problem that we are trying to solve in this issue.

Paypal.me account name/description isn't shown a strikethrough style in the Android/iOS App

What is the root cause of that problem?

We pass the strikethrough style to the parent View component and the web inherits Text styles from the View Component but the native does not
And for adding the strikethrough in native we added a code here for title, and here we are passing the strikethrough to the only title

(_.contains(props.style, styles.offlineFeedback.deleted) ? styles.offlineFeedback.deleted : undefined),

What changes do you think we should make in order to solve the problem?

We have to check if the style prop contains the strikethrough styling that we pass from the OfflineWithFeedback component and if it contains then add the strikethrough to the Description Text, to achieve this we have to add these changes

define a const needsStrikeThrough= (_.contains(props.style, styles.offlineFeedback.deleted) ? styles.offlineFeedback.deleted : undefined)
to check if we need to show a strikethrough style for the Text
and pass the needsStrikeThrough to descriptionTextStyle

const descriptionTextStyle = StyleUtils.combineStyles([
styles.textLabelSupporting,
(props.icon ? styles.ml3 : undefined),
styles.lineHeightNormal,
props.title ? descriptionVerticalMargin : undefined,
props.descriptionTextStyle,
]);

note: this change will affect all the pages and will add a strikethrough to the description of all the pages where we have used the MenuItem

What alternative solutions did you explore? (Optional)

If we want to add the strikethrough style on the Payment page then, here we can check if we have to show strikethrough(isOffline and deletion pending action) to the child and then pass the style to MenuItem for descriptionTextStyle

    const needsStrikeThrough = this.props.network.isOffline && item.pendingAction === 'delete';

<MenuItem
onPress={item.onPress}
title={item.title}
description={item.description}
icon={item.icon}
disabled={item.disabled}
iconFill={item.iconFill}
iconHeight={item.iconSize}
iconWidth={item.iconSize}
badgeText={this.getDefaultBadgeText(item.isDefault)}
wrapperStyle={item.wrapperStyle}
shouldShowSelectedState={this.props.shouldShowSelectedState}
isSelected={this.props.selectedMethodID === item.methodID}

    descriptionTextStyle={
        (needsStrikeThrough ? styles.offlineFeedback.deleted : undefined)  
    }
Result

Simulator Screen Shot - iPhone 14 - 2023-05-05 at 10 36 21

@PauloGasparSv
Copy link
Contributor

Hey @trjExpensify I'm assigning myself and will work on this today ok? As commented here this is related to #17903

@trjExpensify
Copy link
Contributor

Hey @trjExpensify I'm assigning myself and will work on this today ok?

Sounds good!

@trjExpensify trjExpensify added the Internal Requires API changes or must be handled by Expensify staff label May 8, 2023
@melvin-bot
Copy link

melvin-bot bot commented May 8, 2023

Job added to Upwork: https://www.upwork.com/jobs/~016feb202f5cafece9

@melvin-bot
Copy link

melvin-bot bot commented May 8, 2023

Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak (Internal)

@trjExpensify
Copy link
Contributor

^^ @rushatgabhane is assigned to review the PR as a C+ already, so I've switched him on here.

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 labels May 15, 2023
@melvin-bot melvin-bot bot changed the title Payments - Paypal.me account isn't "strikethrough'ed" in App after go offline and deleted [HOLD for payment 2023-05-22] Payments - Paypal.me account isn't "strikethrough'ed" in App after go offline and deleted May 15, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label May 15, 2023
@melvin-bot
Copy link

melvin-bot bot commented May 15, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented May 15, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.13-5 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-05-22. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

  • 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

@melvin-bot
Copy link

melvin-bot bot commented May 15, 2023

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:

  • [@rushatgabhane] The PR that introduced the bug has been identified. Link to the PR:
  • [@rushatgabhane] 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:
  • [@rushatgabhane] 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:
  • [@rushatgabhane] Determine if we should create a regression test for this bug.
  • [@rushatgabhane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@trjExpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@melvin-bot melvin-bot bot added Daily KSv2 Overdue and removed Weekly KSv2 labels May 21, 2023
@PauloGasparSv
Copy link
Contributor

Not overdue! Not sure if we should change this back to weekly though

@melvin-bot melvin-bot bot removed the Overdue label May 23, 2023
@trjExpensify
Copy link
Contributor

Daily is good now that payment is due. @rushatgabhane - I've sent a $1,000 offer to Satish for the C+ review on this job.

Can you please complete the checklist so we can close this out and issue payment? Thanks!

@trjExpensify
Copy link
Contributor

Did you delete your commentary? 😅

@rushatgabhane
Copy link
Member

@trjExpensify actually, this is a new feature! (PR: #18524)

We added strikethrough feature to MenuItem row when deleting it whilst being offline!

@rushatgabhane
Copy link
Member

I believe that bugzero checklist isn't applicable since it's a new feature.

@rushatgabhane
Copy link
Member

rushatgabhane commented May 25, 2023

Nevermind ignore me. It clearly fails the offline tests here - #17903

@rushatgabhane
Copy link
Member

rushatgabhane commented May 25, 2023

  1. The PR that introduced the bug has been identified. Link to the PR: If Paypal.me account is deleted while offline then show it as pending until back online #17903

  2. 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: If Paypal.me account is deleted while offline then show it as pending until back online #17903 (comment)

  3. 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: PR reviewers didn't follow the reviewer checklist, and are made aware of. No further discussion needed

  4. Determine if we should create a regression test for this bug. No because QA caught it.

  5. If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again - N.A.

@rushatgabhane
Copy link
Member

checklist done! @trjExpensify

@trjExpensify
Copy link
Contributor

Perfect. Works for me! Settled up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Internal Requires API changes or must be handled by Expensify staff
Projects
None yet
Development

No branches or pull requests

6 participants