Skip to content

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

Closed

Description

@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

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 19, 2023
  2. MelvinBot commented on Apr 19, 2023

    @MelvinBot
    Contributor

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

  3. MelvinBot commented on Apr 19, 2023

    @MelvinBot
    Contributor

    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
  4. MelvinBot commented on Apr 25, 2023

    @MelvinBot
  5. MelvinBot commented on Apr 27, 2023

    @MelvinBot
  6. MelvinBot commented on May 2, 2023

    @MelvinBot
  7. MelvinBot commented on May 2, 2023

    @MelvinBot
  8. MelvinBot commented on May 3, 2023

    @MelvinBot
  9. melvin-bot commented on May 5, 2023

    @melvin-bot
  10. 7 remaining items

  11. melvin-bot commented on May 12, 2023

    @melvin-bot

    Triggered auto assignment to @AndrewGable (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

  12. greg-schroeder commented on May 12, 2023

    @greg-schroeder
    Contributor

    This is a dev-only bug - applying Engineering for help with reproduction.

    Hey @AndrewGable can you help me reproduce this in DEV?

  13. greg-schroeder commented on May 15, 2023

    @greg-schroeder
    Contributor

    Hoping @AndrewGable can jump in soon!

  14. AndrewGable commented on May 15, 2023

    @AndrewGable
    Contributor

    I cannot reproduce this

  15. Victor-Nyagudi commented on May 16, 2023

    @Victor-Nyagudi
    Contributor

    @AndrewGable Could it be this issue was fixed by this PR?

    I found another potential candidate that could've fixed it. This one seems likelier.

    What do you think?

  16. AndrewGable commented on May 16, 2023

    @AndrewGable
    Contributor

    I'm not quite sure which PR fixed it, I'd be curious why we are investigating that? Thank you!

  17. Victor-Nyagudi commented on May 17, 2023

    @Victor-Nyagudi
    Contributor

    @AndrewGable Just checking if I'm eligible for the reporting bonus.

    The contribution guidelines say that if an issue is reported but is fixed by a PR not associated with it, if the bug reporter can find the PR and prove the bug report came first, they would be eligible for the reporting bonus.

    If the bug is fixed by a PR that is not associated with your bug report, then you will not be eligible for the corresponding compensation unless you can find the PR that fixed it and prove your bug report came first.

  18. AndrewGable commented on May 17, 2023

    @AndrewGable
    Contributor

    @greg-schroeder can determine this for you, thanks!

  19. greg-schroeder commented on May 17, 2023

    @greg-schroeder
    Contributor

    What are your Upwork details @Victor-Nyagudi ?

  20. Victor-Nyagudi commented on May 18, 2023

    @Victor-Nyagudi
    Contributor
  21. greg-schroeder commented on May 18, 2023

    @greg-schroeder
    Contributor

    Sent you an offer for the reporting bonus

  22. Victor-Nyagudi commented on May 18, 2023

    @Victor-Nyagudi
    Contributor

    @greg-schroeder Thank you.

    I've accepted it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringNeeds ReproductionReproducible steps needed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions