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

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:

Run nom run android in the terminal.
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

https://user-images.githubusercontent.com/43996225/233156883-632d1b62-499e-486c-80a3-69b3dcc68a03.mov

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