You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
DEV: Invalid prop-type console warning after launching the app in development. Persists after reloading the app, even multiple times. #17674
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
@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.
Activity
MelvinBot commentedon Apr 19, 2023
Triggered auto assignment to @greg-schroeder (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.MelvinBot commentedon Apr 19, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)MelvinBot commentedon Apr 25, 2023
MelvinBot commentedon Apr 27, 2023
MelvinBot commentedon May 2, 2023
MelvinBot commentedon May 2, 2023
MelvinBot commentedon May 3, 2023
melvin-bot commentedon May 5, 2023
7 remaining items
melvin-bot commentedon May 12, 2023
Triggered auto assignment to @AndrewGable (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.greg-schroeder commentedon May 12, 2023
This is a dev-only bug - applying
Engineeringfor help with reproduction.Hey @AndrewGable can you help me reproduce this in DEV?
greg-schroeder commentedon May 15, 2023
Hoping @AndrewGable can jump in soon!
AndrewGable commentedon May 15, 2023
I cannot reproduce this
Victor-Nyagudi commentedon May 16, 2023
@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?
AndrewGable commentedon May 16, 2023
I'm not quite sure which PR fixed it, I'd be curious why we are investigating that? Thank you!
Victor-Nyagudi commentedon May 17, 2023
@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.
AndrewGable commentedon May 17, 2023
@greg-schroeder can determine this for you, thanks!
greg-schroeder commentedon May 17, 2023
What are your Upwork details @Victor-Nyagudi ?
Victor-Nyagudi commentedon May 18, 2023
@greg-schroeder My Upwork profile link: https://www.upwork.com/freelancers/~0136b5e59ffbb32395
greg-schroeder commentedon May 18, 2023
Sent you an offer for the reporting bonus
Victor-Nyagudi commentedon May 18, 2023
@greg-schroeder Thank you.
I've accepted it.