-
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
When pressing send the send button gets deactivates, then activated, and finally deactivated causing a flashing #46328
Comments
Triggered auto assignment to @zanyrenney ( |
I reported this bug while working on the composer in this issue: I am Hanno from Margelo, an expert agency, and I'd like to work on this issue (feel free to assign me) 😊 |
thanks @hannojg |
how are you getting on with this one @hannojg please ensure to give progress updates according to the cadence listed on the labels. e.g. daily in this case. Thank you! |
Thank you, I was waiting for this composer PR to get merged first: now that its merged I will look into that issue today and provide updates along the way! 😊 |
Not reproducible for me from |
Let me try and test quickly. |
Also can't reproduce so probably yes fixed with your latest PR @hannojg - nice! Thank you! |
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.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
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
Expensify/Expensify Issue URL:
Issue reported by: @hannojg
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1721898827637189
Action Performed:
Send
buttonExpected Result:
Message send without any issues
Actual Result:
When pressing send the send button gets deactivates, then activated, and finally deactivated causing a flashing
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
RPReplay_Final1721898736.MP4
RPReplay_Final1722024018.MP4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: