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
1.go to any chat
2. type text and use semi colon syntax to show emoji suggestions(like 😄)
Expected Result: should not show any console error
Actual Result: shows console error(Invalid prop preferredSkinToneIndex of type string supplied to EmojiSuggestions, expected number. )
Expected Result:
should not show any console error
Actual Result:
shows console error(Invalid prop preferredSkinToneIndex of type string supplied to EmojiSuggestions, expected number. )
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?: n/a Reproducible in production?: n/a 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
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.go to any chat
2. type text and use semi colon syntax to show emoji suggestions(like 😄)
Expected Result: should not show any console error
Actual Result: shows console error(Invalid prop
preferredSkinToneIndexof typestringsupplied toEmojiSuggestions, expectednumber. )Expected Result:
should not show any console error
Actual Result:
shows console error(Invalid prop
preferredSkinToneIndexof typestringsupplied toEmojiSuggestions, expectednumber. )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?
Version Number: dev

Reproducible in staging?: n/a
Reproducible in production?: n/a
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
Simulator.Screen.Recording.-.iPhone.13.-.2023-05-05.at.19.10.18.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1683294088031149
View all open jobs on GitHub
Upwork Automation - Do Not Edit