Room details - Chair icon is missing when tap room name to view the details

[kavimuru]

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. Launch the app and log in expensifail account
2. Tap on any room created or Open Default Room (#admins and #announce) Settings.
3. Check chair icon

Expected Result:

Chair icon is displayed in room details

Actual Result:

Chair icon is missing in room details

Workaround:

Unknown visual

Platform:

Where is this issue occurring?

• iOS
• Android
• Desktop App

Version Number: 1.1.42.3
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): applausetester+0707abb@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

Expensify/Expensify Issue URL:
Issue reported by: Applause
Slack conversation:

View all open jobs on GitHub

[OSBotify]

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

[MelvinBot]

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

[Julesssss]

CC @TomatoToaster

[Julesssss]

I believe this is due to the cherry-pick issue we had earlier this week: #8054 (comment)

Though it should have been fixed in the last hour or two as the follow-up PR was merged 😕

[francoisl]

Oh but that was the revert because we had this weird situation where OptionsListUtils.getAvatarSources was missing, right? Shouldn't we revert the revert now basically?
I'll run some quick tests locally.

[francoisl]

Oh, but it was already cherry-picked about an hour ago #8058 (comment). It's fixed for me on 1.1.42-4, so let's rerun this just to confirm.

[francoisl]

Yeah this definitely looks fixed on v1.1.42-4, closing.