-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Android & iOS - Composer - Selected emoji is not shown in the composer after sending message #46024
Comments
Triggered auto assignment to @rlinoz ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
We think that this bug might be related to #vip-vsp |
Removing the Web-E blocker label, since this is on the app composer. |
Might have been caused by my PR, will take a look tmrw, feel free to assign me! Interesting side note: you can still press send and the emojis will be send to chat, its just that the composer seem to be stuck |
We CP'd the revert and it fixed the issue. |
Let's close this one since the issue is fixed by the revert. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.11-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
The selected emoji will be shown in the composer
Actual Result:
The selected emoji is not shown in the composer after sending message
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6550547_1721742749885.ScreenRecording_07-23-2024_21-15-40_1.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: