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-09-04] Text is overlapping in the main chat window #25648

Closed
1 of 6 tasks
sakluger opened this issue Aug 22, 2023 · 28 comments
Closed
1 of 6 tasks
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Engineering Weekly KSv2

Comments

@sakluger
Copy link
Contributor

sakluger commented Aug 22, 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!


Action Performed:

  1. Clicked on a push notification for a new message, which opened NewDot to that message

Expected Result:

The text should be shown in chronological order of how it was sent

Actual Result:

Some chat messages are overlapping others. When I hover over the message, it flashes.

Overlapping text

Workaround:

N/A

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: v1.3.56-0
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): sasha@expensify.com, jessica.dooley@team.expensify.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Screenshots from jessica.dooley@team.expensify.com:

image

image

image

Expensify/Expensify Issue URL:
Issue reported by: @sakluger
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692664635223199

View all open jobs on GitHub

@sakluger sakluger added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Aug 22, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 22, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 22, 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

@OSBotify
Copy link
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.

@melvin-bot
Copy link

melvin-bot bot commented Aug 22, 2023

Triggered auto assignment to @MonilBhavsar (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@spcheema
Copy link
Contributor

Reproducible on staging:

image

Also on hover, there is a console error.

image

@roryabraham
Copy link
Contributor

Potential dupe of #25616, but should still be addressed with urgency

@roryabraham
Copy link
Contributor

Looks like it might be fixed by #25613 cc @Li357

@situchan situchan mentioned this issue Aug 22, 2023
59 tasks
@MonilBhavsar
Copy link
Contributor

I am not able to reproduce this. @dylanexpensify could you please check if you're able to reproduce this?

@dylanexpensify
Copy link
Contributor

On it now

@dylanexpensify
Copy link
Contributor

Unable to reproduce on staging as well @MonilBhavsar @roryabraham (also @Li357 is OOO now)

@MonilBhavsar
Copy link
Contributor

Thanks! I'll comment in the slack.
@spcheema looks like you were able to reproduce this issue. Do you have any specific clear steps to reproduce?

@MonilBhavsar
Copy link
Contributor

Posted here in slack https://expensify.slack.com/archives/C049HHMV9SM/p1692694595371789?thread_ts=1692664635.223199&cid=C049HHMV9SM

@spcheema
Copy link
Contributor

@MonilBhavsar Here is the video

https://www.loom.com/share/14427568487f42178ed1f89363cade7b?sid=390c0339-4bc1-4b82-bf83-be6cf7763492

Seems like some issue with formatted messages.

@dylanexpensify
Copy link
Contributor

Woof, still cannot reproduce

@spcheema
Copy link
Contributor

Not sure then but I have cleared the cache and removed the local DB to test. You can use my account if needed.

@MonilBhavsar
Copy link
Contributor

MonilBhavsar commented Aug 22, 2023

Thanks! I have been able to reproduce by sending long quoted message

> Hello



> Yes, long quotes

@MonilBhavsar MonilBhavsar removed the Needs Reproduction Reproducible steps needed label Aug 22, 2023
@spcheema
Copy link
Contributor

@MonilBhavsar Is this regression from another issue or open for proposals?

@MonilBhavsar
Copy link
Contributor

It does seem like regression, as it is only happening on staging. I'm currently checking the list of PR's

@Li357
Copy link
Contributor

Li357 commented Aug 22, 2023

I think we can address this quickly. The regression is due to a styling I added for receipt scanning that had unintended effects.

@melvin-bot
Copy link

melvin-bot bot commented Aug 22, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@MonilBhavsar
Copy link
Contributor

Thank you @Li357 ! Mind linking the PR that you think caused this

@dangrous
Copy link
Contributor

This may be the same as #25678, caused by #24235 (comment)

@melvin-bot
Copy link

melvin-bot bot commented Aug 22, 2023

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

@tjferriss
Copy link
Contributor

Applause reported a similar issue happening on iPad #25478. I have also seen my text overlapping recently.

@mountiny mountiny removed the DeployBlockerCash This issue or pull request should block deployment label Aug 23, 2023
@mountiny
Copy link
Contributor

This is fixed in the latest staging and reported internally so closing

@melvin-bot melvin-bot bot added Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Weekly KSv2 labels Aug 28, 2023
@melvin-bot melvin-bot bot changed the title Text is overlapping in the main chat window [HOLD for payment 2023-09-04] Text is overlapping in the main chat window Aug 28, 2023
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Aug 28, 2023
@melvin-bot
Copy link

melvin-bot bot commented Aug 28, 2023

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

@melvin-bot
Copy link

melvin-bot bot commented Aug 28, 2023

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.57-6 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-09-04. 🎊

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 Aug 28, 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:

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

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. Engineering Weekly KSv2
Projects
None yet
Development

No branches or pull requests

10 participants