[HOLD for payment 2023-12-20] [$500] Copy to Clipboard- Email displayed inconsistently in mweb and Android

[izarutskaya]

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: 1.3.96-9
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @

Action Performed:

1. Launch app
2. Tap on a report
3. Send the mail [email protected]
4. Long press the message sent and note the email displayed in copy to clipboard section
5. Go to https://staging.new.expensify.com/
6. Repeat step 2 -- step 4

Expected Result:

In Copy to clipboard section, in both mweb and Android, email should be displayed in the same format in a consistent manner.

Actual Result:

Copy to clipboard section in(.com) shows till "c" in one line (applausetester+06075lsn@

applause.expensifail.c
om) in mweb and shows(.com) in second line (applausetester+06075lsn@

applause.expensifail
.com) in Android.

The displayed email format differs and it is inconsistent in mweb and Android.

Workaround:

Unknown

Platforms:

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

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6267016_1699346542274.mail.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0123a768f29d8cc1b6
• Upwork Job ID: 1721861002279923712
• Last Price Increase: 2023-11-07

Issue Owner

Current Issue Owner: @kevinksullivan

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~0123a768f29d8cc1b6

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[artus9033]

Hi, I'm Artur from Callstack - expert contributor group - and I would like to work on this issue.

[melvin-bot]

📣 @artus9033! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[melvin-bot]

✅ Contributor details stored successfully. Thank you for contributing to Expensify!

[mananjadhav]

Thanks for the interest @artus9033. Can you post a small proposal with what changes so that we're aligned.

🎀 👀 🎀 C+ reviewed.

[melvin-bot]

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

[Julesssss]

Getting Callstack involved sounds good to me

[melvin-bot]

📣 @mananjadhav Please request via NewDot manual requests for the Reviewer role ($500)

[melvin-bot]

The BZ member will need to manually hire artus9033 for the Contributor role. Please store your Upwork details and apply to our Upwork job so this process is automatic in the future!

[artus9033]

@Julesssss thanks, however from mail notifications it seems like something strange happened and somebody assigned their Upwork details as mine through melvinbot? It definitely wasn't me. Could you take a look at this and unassign if that's what happened?

[Julesssss]

however from mail notifications it seems like something strange happened and somebody assigned their Upwork details as mine through melvinbot?

Can you forward the email to me please ([email protected]), I'm not sure exactly what you mean but can take a look

[artus9033]

Sure thing

[Julesssss]

Yeah, somebody seems to have added their details in place of Artur's. Investigating...

[artus9033]

Daily update: issue identifed, solution found; working on a proposal

[artus9033]

Update: I'll be ooo until Wednesday, when I am planning to submit the proposal

[melvin-bot]

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

[melvin-bot]

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

• fix: unify word breaking in ContextMenuItem for Android mweb and Android native #31116

If no regressions arise, payment will be issued on 2023-12-20. 🎊

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

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

• @mananjadhav requires payment through NewDot Manual Requests
• @artus9033 requires payment (Needs manual offer from BZ)

[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:

• [@mananjadhav] The PR that introduced the bug has been identified. Link to the PR:
• [@mananjadhav] 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:
• [@mananjadhav] 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:
• [@mananjadhav] Determine if we should create a regression test for this bug.
• [@mananjadhav] 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.
• [@kevinksullivan] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[kevinksullivan]

Hey @mananjadhav please fill out the checklist above when you get a chance. Thanks!

[mananjadhav]

I don't think we have any offending PR for this one. We changed the behavior of word-break styling. I am on the fence for this one regarding regression test. It's a small feature and I don't think we need one. @Julesssss what are your thoughts?

[Julesssss]

I agree

[Julesssss]

Ready for payment

[mananjadhav]

@kevinksullivan can you please post the payout summary for this one?

[kevinksullivan]

Summary

• Contributor: @artus9033 $500
• C+: @mananjadhav $500

[kevinksullivan]

Hi @artus9033 can you apply to the job and let me know when you've done so?

https://www.upwork.com/jobs/~0123a768f29d8cc1b6

[mananjadhav]

Thanks for summary @kevinksullivan. The payout is only for me here for C+ review. @artus9033 is from Callstack (mentioned here).

[artus9033]

That's right, thanks for the explanation @mananjadhav

[melvin-bot]

@mananjadhav, @artus9033, @Julesssss, @kevinksullivan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[JmillsExpensify]

$500 payment approved for @mananjadhav based on summary above.

[melvin-bot]

@mananjadhav, @artus9033, @Julesssss, @kevinksullivan Eep! 4 days overdue now. Issues have feelings too...

[melvin-bot]

@mananjadhav, @artus9033, @Julesssss, @kevinksullivan Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it!

[melvin-bot]

@mananjadhav, @artus9033, @Julesssss, @kevinksullivan 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[melvin-bot]

@mananjadhav, @artus9033, @Julesssss, @kevinksullivan 10 days overdue. Is anyone even seeing these? Hello?

[Julesssss]

Hey @mananjadhav has the payment been accepted?

[mananjadhav]

Yes @Julesssss Payment is done. We can close this one out.