[HOLD for payment 2025-02-06] [HOLD for payment 2025-02-05] WS - There is an error when the admin clicks on the owner's profile on the members page

[mitarachim]

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.0.90-0
Reproducible in staging?: Yes
Reproducible in production?: No
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: https://expensify.testrail.io/index.php?/tests/view/5514592&group_by=cases:section_id&group_order=asc&group_id=229065
Email or phone of affected tester (no customers): n/a
Issue reported by: Applause Internal Team
Device used: Mac 15.2/Safari
App Component: Workspace Settings

Action Performed:

1. Navigate to https://staging.new.expensify.com/
   Owner (expensifail account)
2. Create a Workspace
   2.Navigate to members and add a member you have access to
3. Select the new member and set them as admin

Admin (expensifail account)

1. Log in as the new set Admin
2. Navigate to workspace editor
3. Navigate to members
4. Click on the Owner of the workspace

Expected Result:

Admin can see the Owner's profile

Actual Result:

"Uh-oh, something went wrong!" when an Admin clicks on the owner's profile

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6725771_1738039712720.Recording__505.mp4

Logs.log

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @muttmuure

[melvin-bot]

Triggered auto assignment to @muttmuure (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]

Triggered auto assignment to @lakchote (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

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

[hungvu193]

Offending PR: #55591
We forgot to import React inside ButtonDisabledWhenOffline component.

// ButtonDisabledWhenOffline component
+ import React from 'react';

[jjcoffee]

cc @truph01 are you able to raise a fix?

[truph01]

I've opened a draft PR here. Could someone please assign this issue to @jjcoffee so the bot can mark him as the C+ to review the PR?

[lakchote]

I've opened a draft PR here. Could someone please assign this issue to @jjcoffee so the bot can mark him as the C+ to review the PR?

Done.

[truph01]

Thanks @hungvu193 for your comment. PR is ready @jjcoffee.

[hungvu193]

I think this kind of bug can be avoided if we write unit test for it. So if it's not urgent, I think you can write a test to make sure ButtonDisabledWhenOffline renders correctly 😄

[lakchote]

I think this kind of bug can be avoided if we write unit test for it. So if it's not urgent, I think you can write a test to make sure ButtonDisabledWhenOffline renders correctly 😄

@truph01 could you do that in a follow up PR please?

Let's not block deployment, but make sure this doesn't happen again too.

[lakchote]

CP requested in https://expensify.slack.com/archives/C07J32337/p1738059506959279.

[yuwenmemon]

Removing the label as the fix has been deployed.

[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 9.0.90-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] fix: missing React import #55843

If no regressions arise, payment will be issued on 2025-02-05. 🎊

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

• @jjcoffee requires payment through NewDot Manual Requests

[melvin-bot]

@jjcoffee @muttmuure @jjcoffee The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[jjcoffee]

No payment required - this is a regression fix.

[melvin-bot]

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

• [CP Staging] fix: missing React import #55843

If no regressions arise, payment will be issued on 2025-02-06. 🎊

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

• @jjcoffee requires payment through NewDot Manual Requests

[melvin-bot]

@jjcoffee @muttmuure @jjcoffee The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

Payment Summary

Upwork Job

• Reviewer: @jjcoffee owed $250 via NewDot

BugZero Checklist (@muttmuure)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[jjcoffee]

No payment required - this is a regression fix.

[melvin-bot]

@lakchote, @jjcoffee, @muttmuure Whoops! This issue is 2 days overdue. Let's get this updated quick!

[melvin-bot]

@lakchote, @jjcoffee, @muttmuure 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[jjcoffee]

@muttmuure This can be closed.

[melvin-bot]

@lakchote, @jjcoffee, @muttmuure 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[lakchote]

Closing the issue as no payment is due (regression fix), as @jjcoffee commented here.