DEV: Invalid prop-type console warning after launching the app in development. Persists after reloading the app, even multiple times.

[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. Run nom run android in the terminal.
2. Wait until app is done loading

Expected Result:

No console warnings or errors.

Actual Result:

Console warning that says:
Warning: Failed prop type: Invalid prop personalDetails.concierge@expensify.com.avatar of type function supplied to WithCurrentUserPersonalDetails(withWindowDimensions(Component)), expected string.

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: DEV
Reproducible in staging?: Needs reproduction
Reproducible in production?: Needs reprouction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

expensify-personalDetails-warning-android.mov

Expensify/Expensify Issue URL:
Issue reported by: @Victor-Nyagudi
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1681882924183879

View all open jobs on GitHub

[MelvinBot]

Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

@greg-schroeder Eep! 4 days overdue now. Issues have feelings too...

[MelvinBot]

@greg-schroeder 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[MelvinBot]

@greg-schroeder 12 days overdue. Walking. Toward. The. Light...

[MelvinBot]

@greg-schroeder 12 days overdue. Walking. Toward. The. Light...

[MelvinBot]

@greg-schroeder this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[melvin-bot]

This issue has not been updated in over 14 days. @greg-schroeder eroding to Weekly issue.