Task - After going offline second time "Assignee" field gets greyed out

[izarutskaya]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: v9.0.13-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers): ilinaiuliia8313+072524@gmail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

1. Open the testing app.
2. Go to any Task report
3. Disable the internet connection
4. Update task title/description/assignee
5. Verify that the updated fields are greyed out
6. Enable the internet connection on the device
7. Verify that fields are not greyed out
8. Disable the internet connection again
9. Verify that fields are not greyed out

Expected Result:

The fields in the Task Report are not greyed out after going offline second time (after update and being online).

Actual Result:

The "Assignee" field gets greyed out when going offline second time.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6554994_1722119359793.Assignee_field_greyed_out.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @kevinksullivan (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 @iwiznia (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[izarutskaya]

Production

Recording.2655.mp4

[iwiznia]

Almost sure this is not a backend problem, removing DB label