You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[C+ Checklist Needs Completion] [$250] Categories - Checkmark appears briefly next to the toggle after exiting selection mode #61823
Version Number: 9.1.43-7 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exp Email or phone of affected tester (no customers):applausetester+khcategory19@applause.expensifail.com Issue reported by: Applause Internal Team Device used: Samsung Galaxy Z Fold 4 / Android 14 App Component: Workspace Settings
Action Performed:
Go to staging.new.expensify.com
Go to workspace settings > Categories.
Long press on any category.
Tap Select.
Tap app back button to exit selection mode.
Expected Result:
Checkmark will not appear next to the toggle after exiting selection mode.
Actual Result:
Checkmark appears briefly next to the toggle after exiting selection mode.
This issue also happens to Members, Tags, Taxes, Per diem etc.
👋 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.
changed the title [-][Due for payment 2025-05-20] [$250] Categories - Checkmark appears briefly next to the toggle after exiting selection mode[/-][+][C+ Checklist Needs Completion] [$250] Categories - Checkmark appears briefly next to the toggle after exiting selection mode[/+]on May 28, 2025
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] 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: NA
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Open the App
Go to workspace settings > Categories.
Long press on any category.
Tap Select.
Tap app back button to exit selection mode
Verify checkmark not appear next to the toggle after exiting selection mode
Activity
melvin-bot commentedon May 10, 2025
Triggered auto assignment to @greg-schroeder (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon May 10, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon May 10, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon May 10, 2025
👋 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:
techievivek commentedon May 12, 2025
@daledah Could this also be related to your PR here #60488? Do you mind taking a look.
39 remaining items
DylanDylann commentedon May 28, 2025
@techievivek @mountiny Could you please help to handle payment to me and the contributor on this issue?
techievivek commentedon May 28, 2025
Hi, yes, sorry I didn't reliaze we had a different author/C+ reviewing the PR.
techievivek commentedon May 28, 2025
@greg-schroeder Can you handle the payment for @DylanDylann and @thelullabyy
greg-schroeder commentedon May 28, 2025
I've been OOO, apologies for the delay. 👀
greg-schroeder commentedon May 28, 2025
Payment summary:
Contributor: @thelullabyy - $250 - Upwork
C+: @DylanDylann - $250 - You can make a manual request via ND for payment
greg-schroeder commentedon May 28, 2025
@DylanDylann Can you complete the checklist for this issue so we can close it out re: discussion + regression testing?
[-][Due for payment 2025-05-20] [$250] Categories - Checkmark appears briefly next to the toggle after exiting selection mode[/-][+][C+ Checklist Needs Completion] [$250] Categories - Checkmark appears briefly next to the toggle after exiting selection mode[/+]greg-schroeder commentedon May 28, 2025
Ah, shoot, I paid you by mistake for this issue @allgandalf given the confusion and multiple assignments. I've requested a refund via Upwork.
EDIT:
We're leaving the payment from this contract in place. We canceled a matching payment for @allgandalf here instead to even things out.
DylanDylann commentedon May 28, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] 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: NA
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Test:
Do we agree 👍 or 👎
greg-schroeder commentedon Jun 3, 2025
filed test, closing
JmillsExpensify commentedon Aug 7, 2025
$250 approved for @DylanDylann