-
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
[HOLD for payment 2023-08-07] [$8000] The message got sent but it also stayed in the compose box #10148
Comments
Triggered auto assignment to @pecanoro ( |
I was able to reproduce on my phone, so assigning external. |
Triggered auto assignment to @dylanexpensify ( |
I think its duplicate of #4129 |
@mateusbra Thanks! We are aware of that, it is mentioned in the issue body. That issue got very long and hard to follow so we decided to make a clean start and just refer to it. Lots of time has passed since then so maybe easier and cleaner solutions will pop up. |
This #8592 (comment) proposal I have explained why this happens and also provided a solution (except mobile safari) that can solve this issue, as well as another issue, of blue opacity issue, remains in iOS after spell check #8592 |
@dylanexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Getting on it today |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane ( |
Triggered auto assignment to @AndrewGable ( |
@dhairyasenjaliya I'm sorry, I'm not sure if I understand. Can you please write up a proposal on this issue, thanks! |
actually this issue I have discussed here #8592 (comment) before, but I have not reported this bug on slack and also I did write a proposal there in order to solve Currently, I'm waiting for the internal team here #8592 (comment) they decide to split mWeb and iOS as 2 separate issues once I get to know what's next step I will notify you here as well |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.47-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-08-07. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Referring to this slack entry here, it does not look like this issue is resolved with the current fix. |
@rojiphil looks like that bug report is 2 days ago. But the fix was deployed to production today. Commented in slack if they can still repro it. Not reproducible on latest release V1.3.48-5 screen-20230803-100700.mp4 |
|
Created a manual request on new dot - https://staging.new.expensify.com/r/5267744771377329 |
Since this is done.... just a reminder that I was the first reporter for this issue as I mention here. |
@dylanexpensify should we pay a bug reporting bonus to @ahmdshrif ? |
Related, can you summarize the appropriate payments for everyone on this issue? |
Yes! Sorry, got stuck with travel yesterday! |
Payment summary:
Upwork job is here. |
@dylanexpensify applied. |
Hello, my name is Francisco Castellanos. I am a systems engineering student and a junior web designer. I saw the job posting and I believe it fits well with my profile. I have completed courses in HTML, CSS, JavaScript, MongoDB, PHP, React, and Node.js. |
📣 @Fco18! 📣
|
@ahmdshrif sent offer! |
Reviewed the details for @rushatgabhane. This amount is approved for payment in NewDot. |
@dylanexpensify accepted! |
Payments/contracts done! |
Seems like issue still exists. There are multiple bug reports for this. @c3024 maybe you can help with consistent reproducible step here. |
@aimane-chnaif |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
Expected Result:
Compose box should clear
Actual Result:
Compose box doesn't clear
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.85-8
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
related to #4129
RPReplay_Final1659025442.MP4
Expensify/Expensify Issue URL:
Issue reported by: @mountiny
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1658727800463809
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: