[HOLD for payment 2023-10-23] [$500] Android native - Default Scrollbar is visible when scrolling in a chat

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:

Launch app
Tap on a report
Scroll the page up and down

Expected Result:

Open any report in LHN, a white line must not appear on left side while scrolling the page up and down.

Actual Result:

Open any report in LHN, User can see a white line appears on left side while scrolling the page up and down.

Workaround:

Unknown

Platforms:

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

Version Number: 1.3.72-6

Reproducible in staging?: Y

Reproducible in production?: N

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

Bug6208418_scrol.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/~01e7fb1a538e34bc1d
Upwork Job ID: 1705059508445011968
Last Price Increase: 2023-10-06
Automatic offers:

abdulrahuman5196 | Reviewer | 26938079
situchan | Contributor | 26938083
bernhardoj | Contributor | 27130414

@lschurr

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

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

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

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

@cristipaval

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

I can see this issue on production as well

@s-alves10 This is reproducible to me with the latest Staging version but it isn't reproducible with the latest production (1.3.69-2). Could you please check what is your production version where you can reproduce?

@abdulrahuman5196

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

Fix report screen scrollbar on Android is on the left screen #29253

If no regressions arise, payment will be issued on 2023-10-23. 🎊

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:

@abdulrahuman5196 requires payment offer (Reviewer)
@bernhardoj requires payment offer (Contributor)

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

@abdulrahuman5196

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:

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

@abdulrahuman5196

@abdulrahuman5196 - Could you work on the checklist for this one?

@bernhardoj

Payment summary:

Bug reporter: Applause (no payment)
Contributor: @bernhardoj $750
Contributor+: @abdulrahuman5196 $750

Payments have been made in Upwork.

@lschurr

The PR that introduced the bug has been identified. Link to the PR:
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:
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:

Not a regression per say, since we had a patch and the patch is not working after the update.

Determine if we should create a regression test for this bug.

Yes. If not already present.

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.

Open any chat with enough messages to scroll
Verify the scrollbar is on the right side of the screen
Verify the chat list is inverted, i.e. you need to scroll from bottom to top

@lschurr

Great! This is complete.

Navigation Menu

Repository navigation

[HOLD for payment 2023-10-23] [$500] Android native - Default Scrollbar is visible when scrolling in a chat #27931

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Bug0 Triage Checklist (Main S/O)

74 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[HOLD for payment 2023-10-23] [$500] Android native - Default Scrollbar is visible when scrolling in a chat #27931

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Activity

melvin-bot commented on Sep 21, 2023

melvin-bot commented on Sep 21, 2023

Bug0 Triage Checklist (Main S/O)

OSBotify commented on Sep 21, 2023

melvin-bot commented on Sep 21, 2023

dummy-1111 commented on Sep 21, 2023

cristipaval commented on Sep 21, 2023

74 remaining items

melvin-bot commented on Oct 16, 2023

melvin-bot commented on Oct 16, 2023

lschurr commented on Oct 23, 2023

lschurr commented on Oct 23, 2023

lschurr commented on Oct 23, 2023

abdulrahuman5196 commented on Oct 23, 2023

lschurr commented on Oct 23, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions