Disable guides calling if user is blocked from concierge

[puneetlath]

Details

This PR makes it so that if a user is blocked from talking to Concierge they are also blocked from starting a Guides call. cc @stitesExpensify

Fixed Issues

$ #7499

Screen.Recording.2022-02-02.at.4.53.27.PM.mov

Tests

• Verify that no errors appear in the JS console

1. Sign into an account in New Dot and navigate to your Concierge chat
2. Message Concierge
3. Go to https://www.expensify.com.dev/concierge/#/tools/ChatSearchByUser and find the chat with your user
4. Click User Info and block the user
5. Go back to New Dot and try to start a call
6. You should see a growl saying that calling is blocked
7. The call button should become disabled with a warning message above explaining why
8. Close the call modal, refresh the page, and open the call modal again
9. You should still see the call button as disabled with the message above it

QA Steps

• Verify that no errors appear in the JS console

1. Sign into an account in New Dot and navigate to your Concierge chat
2. Message Concierge
3. Go to https://www.expensify.com/concierge/#/tools/ChatSearchByUser and find the chat with your user
4. Click User Info and block the user
5. Go back to New Dot and try to start a call
6. You should see a growl saying that calling is blocked
7. The call button should become disabled with a warning message above explaining why
8. Close the call modal, refresh the page, and open the call modal again
9. You should still see the call button as disabled with the message above it

Tested On

• Web
• Mobile Web
• Desktop
• iOS
• Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

[puneetlath]

@Expensify/design any opinion on red vs gray exclamation icon? This text will appear above the call me button when it is disabled due to a user having been blocked from interacting with concierge/guides.

[michelle-thompson]

I wonder if we could do yellow instead? Red feels extreme in this context.

[timszot]

This looks good to me, but since I'm still learning a lot for newDot, leaving for @stitesExpensify for final review.

[timszot]

Nice edits, thanks!

[MelvinBot]

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

[botify]

@stitesExpensify looks like this was merged without passing tests. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[stitesExpensify]

All tests had passed when this was merged. This is a bug https://github.com/Expensify/Expensify/issues/189984

[francoisl]

#7511 (comment)

We have internal QA on Expensify/App PRs now? Anyway it looks like it's not deployed to staging yet so I'll check again later.

[OSBotify]

🚀 Deployed to staging by @stitesExpensify in version: 1.1.36-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

[francoisl]

Internal QA 👍

[OSBotify]

🚀 Deployed to production by @roryabraham in version: 1.1.36-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅