Concierge - No GBR for Concierge tasks until navigating for the second login

[vincdargento]

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

Action Performed:

1. Navigate to https://staging.new.expensify.com
2. Login with new account - use any onboarding purposes except "Something else option"
3. Navigate to concierge and notice there is a GBR for each tasks and LHN of the concierge
4. Without completing anything log out and log in again with the same account
5. Notice GBR in LHN but no GBR for the concierge tasks until navigating to each tasks

Expected Result:

Until completing tasks, there is GBR for each concierge tasks and LHN in concierge chat.
User can click the box for completing the task in the concierge chat without navigating to the task detail

Actual Result:

GBR in concierge tasks are disappeared for the second login until navigating to each tasks
User can't complete the task in the concierge chat

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

bug.mp4

View all open jobs on GitHub

[melvin-bot]

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

[RachCHopkins]

I don't get the GBR problem, but I do get the inability to check off a task without clicking into it - are we sure this is not deliberate? Will check.

[melvin-bot]

@RachCHopkins Whoops! This issue is 2 days overdue. Let's get this updated quick!