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
mWeb Android/Chrome - Compose box is hidden when we delete edited message #24016
Write some text in compose box and long press message sent in step 3 and edit the message
Remove all the text and click send, in delete popup, click on delete
Observe that composer is now not visible
Expected Result:
App should display the composer after we delete edited message
Actual Result:
App does not display the composer after we delete edited message in android chrome
Workaround:
unknown
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: 1.3.48-3 Reproducible in staging?: Y Reproducible in production?: Needs repro 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
👋 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:
Identify the pull request that introduced this issue and revert it.
@bfitzexpensify We are near closure of the checklist. Contributor is not able to repro on PROD, i need a bit more time to validate PROD. If you can check on your side as well to confirm if its a blocker or no, would be great
Activity
melvin-bot commentedon Aug 1, 2023
Triggered auto assignment to @bfitzexpensify (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Aug 1, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)OSBotify commentedon Aug 1, 2023
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:melvin-bot commentedon Aug 1, 2023
Triggered auto assignment to @marcochavezf (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.mvtglobally commentedon Aug 1, 2023
@bfitzexpensify We are near closure of the checklist. Contributor is not able to repro on PROD, i need a bit more time to validate PROD. If you can check on your side as well to confirm if its a blocker or no, would be great
marcochavezf commentedon Aug 1, 2023
I'm also not able to reproduce it on prod, investigating what caused the issue
kushu7 commentedon Aug 1, 2023
@marcochavezf Issue is from this PR
tested with reverting this PR.
11 remaining items
dummy-1111 commentedon Aug 1, 2023
@s77rt
Can you test with the branch https://github.com/s-alves10/App/tree/fix/issue-24016?
s77rt commentedon Aug 1, 2023
@s-alves10 Please raise a PR, I will test asap. You need to test that as well.
dummy-1111 commentedon Aug 1, 2023
@s77rt
PR is in draft.
Please test with it. I'm testing but it shows an error in android native
s77rt commentedon Aug 1, 2023
@s-alves10 Let's continue proposal discussion here.
marcochavezf commentedon Aug 2, 2023
The PR that caused the regression was reverted, so I'm going to close this issue since it's no longer happening on staging
dhanashree-sawant commentedon Aug 2, 2023
Hi @marcochavezf, @s77rt, it seems like issue was useful to trigger the solution, will it be eligible for reporting bonus?
marcochavezf commentedon Aug 2, 2023
Oh sorry @dhanashree-sawant, I think yes since it was a deploy blocker and fixed with the revert. Reopening for payment cc @bfitzexpensify
bfitzexpensify commentedon Aug 3, 2023
Cool, this has been paid out.
s77rt commentedon Aug 24, 2023
I think this is reproducible again
s77rt commentedon Aug 30, 2023
This actually got reported again https://expensify.slack.com/archives/C049HHMV9SM/p1692747837798019
dummy-1111 commentedon Aug 31, 2023
I think this should be fixed in #23908