[HOLD for Payment 2025-03-25] [$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access #57342

IuliiaHerets · 2025-02-24T20:43:48Z

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: v9.1.5-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 13.6/Chrome
App Component: User Settings

Action Performed:

Go to ND.
Navigate to Settings > Security > Copilot.
Select a user and set Full Access.
Tap Add Copilot.
Enter the magic code, add the user, and click the three-dot menu.
Select Change Access > Limited Access.
Refresh the page.

Expected Result:

User should remain on the Copilot Magic Code page after refreshing.

Actual Result:

User is redirected to the previous page.

Workaround:

Unknown

Platforms:

Screenshots/Videos

Bug6752955_1740428985666.Screen_Recording_2025-02-24_at_12.28.50_PM.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021894288958180956203
Upwork Job ID: 1894288958180956203
Last Price Increase: 2025-03-11
Automatic offers:

ikevin127 | Reviewer | 106518145
daledah | Contributor | 106518147

Issue Owner

Current Issue Owner: @ikevin127

melvin-bot · 2025-02-24T20:43:58Z

Triggered auto assignment to @dylanexpensify (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.

M00rish · 2025-02-24T23:12:13Z

🚨 Edited by proposal-police: This proposal was edited at 2025-02-25 02:11:55 UTC.

Proposal

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

Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access

What is the root cause of that problem?

we're relying on state newRole to show or not the magic code modal :

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Lines 86 to 90 in 2cf14bf

    
           {!!newRole && ( 
        
               <UpdateDelegateMagicCodeModal 
        
                   login={login} 
        
                   role={newRole} 
        
                   isValidateCodeActionModalVisible={isValidateCodeActionModalVisible}

after refresh state will be lost

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

Or use we could do it like add copilot confirm page:

const [isValidateCodeActionModalVisible, setIsValidateCodeActionModalVisible] = useState(showValidateActionModal ?? false);

     useEffect(() => {
        navigation.setParams({showValidateActionModal: isValidateCodeActionModalVisible});
    }, [isValidateCodeActionModalVisible]);

if(isValidateCodeActionModalVisible){
ExpectedRole = currentRole === CONST.DELEGATE_ROLE.SUBMITTER ? CONST.DELEGATE_ROLE.ALL : CONST.DELEGATE_ROLE.SUBMITTER
setNewRole(ExpectedRole)
}
...
{!!newRole && (
                    <UpdateDelegateMagicCodeModal
                        login={login}
                        role={newRole}
                        isValidateCodeActionModalVisible={isValidateCodeActionModalVisible}
                        onClose={() => {
                            setIsValidateCodeActionModalVisible(false);
                        }}

modal stuck issue after sucess:

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateMagicCodeModal.tsx

Lines 32 to 33 in eaa3be4

    
               Navigation.navigate(ROUTES.SETTINGS_SECURITY); 
        
           }, [login, currentDelegate, role, updateDelegateErrors]);

Navigation.goBack(ROUTES.SETTINGS_SECURITY)

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

UI issue

What alternative solutions did you explore?

github-actions · 2025-02-24T23:12:34Z

⚠️ @M00rish Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

daledah · 2025-02-25T03:11:47Z

🚨 Edited by proposal-police: This proposal was edited at 2025-02-25 11:40:24 UTC.

Proposal

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

User is redirected to the previous page.

What is the root cause of that problem?

The condition to show the magic code page are isValidateCodeActionModalVisible and !!newRole, which are always false when the page is mounted:

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Lines 28 to 29 in eaa3be4

    
           const [isValidateCodeActionModalVisible, setIsValidateCodeActionModalVisible] = useState(false); 
        
           const [newRole, setNewRole] = useState<ValueOf<typeof CONST.DELEGATE_ROLE> | null>();

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Line 86 in eaa3be4

{!!newRole && (

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Line 90 in eaa3be4

isValidateCodeActionModalVisible={isValidateCodeActionModalVisible}

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

Update:

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Lines 28 to 29 in eaa3be4

    
           const [isValidateCodeActionModalVisible, setIsValidateCodeActionModalVisible] = useState(false); 
        
           const [newRole, setNewRole] = useState<ValueOf<typeof CONST.DELEGATE_ROLE> | null>();

    const newRoleFromURL = route.params.newRole;
    const [isValidateCodeActionModalVisible, setIsValidateCodeActionModalVisible] = useState(showValidateActionModalFromURL ?? false);
    const [newRole, setNewRole] = useState<ValueOf<typeof CONST.DELEGATE_ROLE> | null>(newRoleFromURL);
    useEffect(() => {
        navigation.setParams({showValidateActionModal: isValidateCodeActionModalVisible, newRole: newRole});
    }, [isValidateCodeActionModalVisible, newRole]);

With this change, we stored the new role and action modal state in URL so that when refreshing the page, the magic modal is shown properly.

In add delegate flow, we used the same logic to handled the similar case:

App/src/pages/settings/Security/AddDelegate/ConfirmDelegatePage.tsx

Line 38 in eaa3be4

    
           const [isValidateCodeActionModalVisible, setIsValidateCodeActionModalVisible] = useState(showValidateActionModal ?? false);

Note: About the bug "we're still left with a visual bug where after the refresh, when the code is added to the input and the change happens, the code modal remains stuck on the screen (without a backdrop):", I can reproduce it in staging as well. It is because of this line:

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateMagicCodeModal.tsx

Line 32 in eaa3be4

Navigation.navigate(ROUTES.SETTINGS_SECURITY);

we should update it to Navigation.goBack(ROUTES.SETTINGS_SECURITY).

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

None

What alternative solutions did you explore? (Optional)

melvin-bot · 2025-02-25T07:30:58Z

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

melvin-bot · 2025-02-25T07:31:03Z

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

ikevin127 · 2025-02-25T11:11:01Z

@daledah Thanks for the proposal, your RCA is not complete as even if we store the isValidateCodeActionModalVisible between refresh, there's another condition which if not true -> the modal will still not show up after refresh.

Your solution is on the right track if we are to compare to the other component you referenced, but is also incomplete, as even if we store both isValidateCodeActionModalVisible and newRole and the modal shows, we're still left with a visual bug where after the refresh, when the code is added to the input and the change happens, the code modal remains stuck on the screen (without a backdrop):

.
@M00rish Thanks for the proposal.

First of all, I have to let you know that removing the: 🚨 Edited by proposal-police: This proposal was edited at 2025-02-25 02:11:55 UTC. from your proposal is not allowed and should not be done for 3 reasons:

your proposal will become invalid and will not be taken into consideration + you risk getting a formal warning
reviewers use that to determine the timeline of an edited proposal which is important for fairness, especialy when there's lots of edits on a proposal
the bot will add it back everytime you remove it because the script checks for the existence of that string and if it doesn't exist will add it back (therefore there's no point in removing it)

Quoting Matt from Slack:

Seems like deleting proposal police text should be a violation of Rule #2, if anyone sees this, please comment in the GH, tag the contributor and reference our https://github.com/Expensify/App/blob/main/CODE_OF_CONDUCT.md

🔄 Regarding your proposal, the RCA is incomplete, similar to the other proposal, you're only mentioning the newRole condition, but even if that is true, the modal will still not show after refresh because isValidateCodeActionModalVisible will be false on component mount.

Your solution is not addressing the fact that neither newRole nor isValidateCodeActionModalVisible are persisted after refresh, which especially in the case of newRole being an important variable that should be persisted, otherwise there won't be any role in the state to be assigned when the API is called. In short: your solutions are only showing the modal because you override the !!newRole check, which disregards the variable therefore creating a regression.

Moving forward, I think PR #54680 is a good starting point since it addressed exactly the same issue, the difference being that with our component (UpdateDelegateRolePage) the newRole variable has to be taken in consideration.

♻ If still interested, I'm looking forward to reviewing the first updated proposal that has a complete RCA and working solution.

M00rish · 2025-02-25T11:21:20Z

@ikevin127 , proposal updated pls review again alternative solution

M00rish · 2025-02-25T11:25:24Z

Your solution is not addressing the fact that neither newRole nor isValidateCodeActionModalVisible are persisted after refresh.

in My RCA i mentioned newRole

we're relying on state newRole to show or not the magic code modal

but I missed isValidateCodeActionModalVisible

(about removing the Edited by proposal-police I did not know thanks for letting me know)

daledah · 2025-02-25T11:27:43Z

Proposal updated

Updated RCA.

ikevin127 · 2025-02-25T11:32:34Z

@M00rish Please carefully read my previous comment, use AI to translate if needed (including on this comment).

Your updated proposal is still invalid because the solution is not presisting the newRole variable when refreshing the page, simply persisting isValidateCodeActionModalVisible is not enough to fix this issue.

♻ As mentioned in my previous comment, simply copy & pasting PRs #54680 fix is not enough for our issue as it's more complex, this is why in order to fix this issue, one needs to take some time and put some thought into it because it's not as simple as a 1-line fix.

M00rish · 2025-02-25T11:43:19Z

@ikevin127, I understood, iI am making a check to see if the code magic modal is on use is switching to the other role , can you review again thanks:
Proposal updated

daledah · 2025-02-25T11:43:20Z

Proposal updated

Updated solution to address bug "where after the refresh, when the code is added to the input and the change happens, the code modal remains stuck on the screen (without a backdrop)"

M00rish · 2025-02-25T12:06:51Z

Edited: proposal updated
for modal stuck issue

LorenzoBloedow · 2025-02-25T14:47:06Z

🚨 Edited by proposal-police: This proposal was edited at 2025-02-25 16:58:13 UTC.

Proposal

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

Copilot code verification modal is not persisted across page refreshes.

What is the root cause of that problem?

The newRole and IsValidateCodeActionModalVisible state variables aren't being persisted across page refreshes.

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

Introduce a new session storage constant, like DELEGATE_NEW_ROLE: 'DELEGATE_NEW_ROLE', this will be stored until the tab is closed (but not refreshed):

App/src/CONST.ts

Lines 6132 to 6137 in e12e4b3

    
           SESSION_STORAGE_KEYS: { 
        
               INITIAL_URL: 'INITIAL_URL', 
        
               ACTIVE_WORKSPACE_ID: 'ACTIVE_WORKSPACE_ID', 
        
               RETRY_LAZY_REFRESHED: 'RETRY_LAZY_REFRESHED', 
        
               LAST_REFRESH_TIMESTAMP: 'LAST_REFRESH_TIMESTAMP', 
        
           },

Store newRole in the session storage (this could be done either in the onSelectRow function or in a new useEffect):

sessionStorage.setItem(CONST.SESSION_STORAGE_KEYS.DELEGATE_NEW_ROLE, option?.value);

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Lines 75 to 82 in e12e4b3

    
           onSelectRow={(option) => { 
        
               if (option.isSelected) { 
        
                   Navigation.dismissModal(); 
        
                   return; 
        
               } 
        
               setNewRole(option?.value); 
        
               setIsValidateCodeActionModalVisible(true); 
        
           }}

3. Create a new useEffect to apply this session storage variable, if it exists:

    useEffect(() => {
        const previousNewRole = sessionStorage.getItem(CONST.SESSION_STORAGE_KEYS.DELEGATE_NEW_ROLE);
        if (previousNewRole && Object.values(CONST.DELEGATE_ROLE).includes(previousNewRole)) {
            setNewRole(previousNewRole);
            setIsValidateCodeActionModalVisible(true);
            sessionStorage.removeItem(CONST.SESSION_STORAGE_KEYS.DELEGATE_NEW_ROLE);
        }
    }, []);

It should be put here:

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateRolePage.tsx

Line 39 in e12e4b3

Update this line

App/src/pages/settings/Security/AddDelegate/UpdateDelegateRole/UpdateDelegateMagicCodeModal.tsx

Line 32 in a59f464

Navigation.navigate(ROUTES.SETTINGS_SECURITY);

to:

Navigation.dismissModal();

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

Simply ensuring the magic code can be entered without additional input after refreshing the page (which means the first modal is the magic code modal) should be enough.

What alternative solutions did you explore? (Optional)

Storing this data with Onyx or local storage but it doesn't seem appropriate since it's a transient value.

LorenzoBloedow · 2025-02-25T16:59:36Z

Proposal Updated

Fixed visual bug where the modal would stay on screen even after applying the right magic code

github-actions · 2025-02-25T17:00:07Z

⚠️ @LorenzoBloedow Thanks for your proposal. Please update it to follow the proposal template, as proposals are only reviewed if they follow that format (note the mandatory sections).

ikevin127 · 2025-02-26T01:27:54Z

Thanks everybody for the proposals!

@daledah's updated proposal makes the most sense to me. The updated RCA is correct, touching on all parts involved in this issue and the proposed solution fixes the issue accordingly, considering the UI issue mentioned in my first review.

♻ The reason why I went with their proposal is because after my first review, they were first to update their proposal to a point where it was complete and had no regressions.

Note

Note for PR

@daledah Please consider taking this fix into account and applying the fix similar to what the referenced PR applied in commit 45c2e9e, since after I tested on iOS: mWeb I noticed the same behaviour - and we should align the behaviour to be the same since that was already approved by the design team in the other PR.

🎀👀🎀 C+ reviewed

melvin-bot · 2025-02-26T01:28:06Z

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

melvin-bot · 2025-03-04T16:00:04Z

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

daledah · 2025-03-06T23:01:02Z

@jasperhuangg Whenever you have a moment, would you mind taking a look at this issue?

melvin-bot · 2025-03-10T09:22:02Z

@jasperhuangg @ikevin127 @dylanexpensify this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

melvin-bot · 2025-03-10T10:16:02Z

@ikevin127 Huh... This is 4 days overdue. Who can take care of this?

ikevin127 · 2025-03-10T16:35:46Z

♻ Still awaiting @jasperhuangg's assignment on my proposal review.

melvin-bot · 2025-03-11T16:00:14Z

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

daledah · 2025-03-11T23:38:53Z

@jasperhuangg This issue is pending your assignment. Could you review it when you have a moment?

dylanexpensify · 2025-03-12T08:00:21Z

Bump @jasperhuangg 🙇‍♂

melvin-bot · 2025-03-13T21:56:01Z

📣 @ikevin127 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

melvin-bot · 2025-03-13T21:56:04Z

📣 @daledah 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

daledah · 2025-03-14T15:43:05Z

@ikevin127 PR is ready.

ikevin127 · 2025-03-20T18:45:53Z

⚠️ Hold for payment automation failed on this issue -> this should be on [HOLD for Payment 2025-03-25] according to 2 days ago (18th of March) production deploy from comment.

cc @dylanexpensify

ikevin127 · 2025-03-25T09:19:51Z

cc @dylanexpensify for payments

dylanexpensify · 2025-03-25T13:03:35Z

Payment summary:

Contributor: @daledah $250 via Upwork
Contributor+: @ikevin127 $250 via Upwork

Please apply/request!

dylanexpensify · 2025-03-25T13:06:07Z

Paid! @ikevin127 can you complete checklist, please

ikevin127 · 2025-03-26T23:36:35Z

BugZero Checklist:

[Contributor] Classify the bug:

Bug classification

Source of bug:

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:

[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: https://github.com/Expensify/App/pull/56231/files#r2015131851.
[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: N/A
[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

Navigate to Settings > Security > Copilot.
Select a user and give them Full Access.
Tap Add Copilot.
Enter the magic code, add the user, then click the three-dot menu.
Select Change Access > Limited Access.
Refresh the page.
Verify that the magic code modal screen remains opened upon page refresh.

Do we agree 👍 or 👎.

dylanexpensify · 2025-04-02T08:23:51Z

done!

IuliiaHerets added Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 labels Feb 24, 2025

melvin-bot bot assigned dylanexpensify Feb 24, 2025

IuliiaHerets changed the title ~~Copilot- Page redirects after refreshing Copilot Magic Code page after changing access~~ Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access Feb 24, 2025

dylanexpensify added the External Added to denote the issue can be worked on by a contributor label Feb 25, 2025

melvin-bot bot changed the title ~~Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access~~ [$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access Feb 25, 2025

melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Feb 25, 2025

melvin-bot bot assigned ikevin127 Feb 25, 2025

melvin-bot bot assigned jasperhuangg Feb 26, 2025

melvin-bot bot added the Overdue label Mar 4, 2025

melvin-bot bot removed the Overdue label Mar 5, 2025

melvin-bot bot added the Overdue label Mar 10, 2025

melvin-bot bot removed the Overdue label Mar 10, 2025

jasperhuangg assigned daledah Mar 13, 2025

melvin-bot bot added Overdue and removed Help Wanted Apply this label when an issue is open to proposals by contributors labels Mar 13, 2025

daledah mentioned this issue Mar 14, 2025

fix: remain magic code modal when reload copilot page #58452

Merged

50 tasks

melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Daily KSv2 Overdue labels Mar 14, 2025

dylanexpensify changed the title ~~[$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access~~ [HOLD for Payment 2025-03-25] [$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access Mar 20, 2025

ikevin127 mentioned this issue Mar 26, 2025

Update delegate flow to use modal #56231

Merged

50 tasks

dylanexpensify closed this as completed Apr 2, 2025

[HOLD for Payment 2025-03-25] [$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access #57342

[HOLD for Payment 2025-03-25] [$250] Web - Copilot- Page redirects after refreshing Copilot Magic Code page after changing access #57342

Comments

IuliiaHerets commented Feb 24, 2025 • edited by melvin-bot bot Loading

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Screenshots/Videos

melvin-bot bot commented Feb 24, 2025

M00rish commented Feb 24, 2025 • edited Loading

Proposal

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

What is the root cause of that problem?

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

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore?

github-actions bot commented Feb 24, 2025

daledah commented Feb 25, 2025 • edited by github-actions bot Loading

Proposal

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

What is the root cause of that problem?

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

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

melvin-bot bot commented Feb 25, 2025

melvin-bot bot commented Feb 25, 2025

ikevin127 commented Feb 25, 2025

M00rish commented Feb 25, 2025 • edited Loading

M00rish commented Feb 25, 2025 • edited Loading

daledah commented Feb 25, 2025

Proposal updated

ikevin127 commented Feb 25, 2025

M00rish commented Feb 25, 2025

daledah commented Feb 25, 2025

Proposal updated

M00rish commented Feb 25, 2025 • edited Loading

LorenzoBloedow commented Feb 25, 2025 • edited by github-actions bot Loading

Proposal

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

What is the root cause of that problem?

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

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

LorenzoBloedow commented Feb 25, 2025

Proposal Updated

github-actions bot commented Feb 25, 2025

ikevin127 commented Feb 26, 2025

Note for PR

melvin-bot bot commented Feb 26, 2025

melvin-bot bot commented Mar 4, 2025

daledah commented Mar 6, 2025

melvin-bot bot commented Mar 10, 2025

melvin-bot bot commented Mar 10, 2025

ikevin127 commented Mar 10, 2025

melvin-bot bot commented Mar 11, 2025

daledah commented Mar 11, 2025

dylanexpensify commented Mar 12, 2025

melvin-bot bot commented Mar 13, 2025

melvin-bot bot commented Mar 13, 2025

daledah commented Mar 14, 2025

ikevin127 commented Mar 20, 2025

ikevin127 commented Mar 25, 2025

dylanexpensify commented Mar 25, 2025

dylanexpensify commented Mar 25, 2025

ikevin127 commented Mar 26, 2025

BugZero Checklist:

Regression Test Proposal

dylanexpensify commented Apr 2, 2025

IuliiaHerets commented Feb 24, 2025 •

edited by melvin-bot bot

Loading

M00rish commented Feb 24, 2025 •

edited

Loading

daledah commented Feb 25, 2025 •

edited by github-actions bot

Loading

M00rish commented Feb 25, 2025 •

edited

Loading

M00rish commented Feb 25, 2025 •

edited

Loading

M00rish commented Feb 25, 2025 •

edited

Loading

LorenzoBloedow commented Feb 25, 2025 •

edited by github-actions bot

Loading