[$8000] Compose box disappears when user edit message and press "New message" button.

[kavimuru]

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. Login with any account
2. Click into a chat that has many messages
3. Mark last message as unread
4. Scroll up so that the "unread" last message is out of view
5. Tap "Edit message" on any of your messages
6. Don't make any changes to the message
7. Tap on the "New Message" button at the top of the screen
8. You are brought down to the "unread" message. Note that the compose box is gone so you cannot write any new messages. 🔴
9. Tap Back to return to chat list
10. Tap into the chat you are testing with again
11. Scroll up to the message you were editing
12. Note that it's still in edit mode and has the "Cancel" and "Save Changes" buttons showing 🔴

Expected Result:

Result expected by Kavi

Composer should be visible and scroll be should be on the right when you open a the report.

Result expected by Sonia

If you tap "New Message" it should bring you to the unread message and should show you the composer at the bottom of the chat. When you leave the chat and go back the message should not remain in edit mode and you should see the composer at the bottom of the chat.

Actual Result:

The Composer is still missing and when you tried to scroll, scroll bar is on the left.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• iOS / native

Version Number: 1.2.72-0
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
Notes/Photos/Videos:

LMDE2559.1.MP4

Screen.Recording.2023-02-16.at.1.55.19.AM.mov

Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1676518791786289

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0152a52b263a42cee8
• Upwork Job ID: 1629212143551795200
• Last Price Increase: 2023-05-15

[MelvinBot]

Triggered auto assignment to @sonialiap (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[MelvinBot]

Bug0 Triage Checklist (Main S/O)

• This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
• This bug is not a duplicate report (check E/App issues and #expensify-bugs)
  • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
• This bug is reproducible using the reproduction steps in the OP. S/O
  • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
  • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
• This issue is filled out as thoroughly and clearly as possible
  • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
• I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

[MelvinBot]

@sonialiap Huh... This is 4 days overdue. Who can take care of this?

[sonialiap]

PrashantMangukiya was able to reproduce

15216-iOS-Reproduction.mov

[sonialiap]

I can reproduce, thanks PrashantMangukiya for correcting the steps I was taking

screenRecording-23-1-2023-11-38.mp4

1. Click into a chat
2. Mark the bottom message as unread
3. Scroll up
4. Select "Edit" on a message you wrote
5. Don't make any changes to the message you're editing
6. Tap on the "New Message" button at the top of the screen
7. You are brought back down to the unread message ✅ . However, the compose box is gone so you cannot write any new messages 🔴

Before taking the above steps

After taking the above steps

8. Go back to chat list
9. Tap into the chat you were testing with again
10. Scroll up to the message you were editing
11. Note that it's still in edit mode and has the "Cancel" and "Save Changes" buttons showing

Current Behavior:

Tapping "New Message" while in edit mode hides the composer at the bottom of the screen. If you tap out of the chat and back in without saving/canceling your edit then the message remains in edit mode until you save or cancel the changes.

Expected Result:

If you tap "New Message" it should bring you to the unread message and should show you the composer at the bottom of the chat. When you leave the chat and go back the message should not remain in edit mode and you should see the composer at the bottom of the chat.

Updated OP with step and Expected Result clarification.

[MelvinBot]

Triggered auto assignment to @chiragsalian (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[sonialiap]

@chiragsalian I agree with Kavi that the composer should be visible at the bottom of the chat even if you're in edit mode on a message higher up in the chat. I cannot reproduce the composer not showing up if you tap out and back into the chat, it shows up for me. I think that edit mode should be canceled when you tap out of the chat, but that is not the issue that was reported here.

[chiragsalian]

Interesting, yeah i can reproduce the issue. Marking it as external.

[MelvinBot]

Job added to Upwork: https://www.upwork.com/jobs/~0152a52b263a42cee8

[MelvinBot]

Current assignee @sonialiap is eligible for the External assigner, not assigning anyone new.

[MelvinBot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat (External)

[MelvinBot]

Current assignee @chiragsalian is eligible for the External assigner, not assigning anyone new.

[PrashantMangukiya]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Whenever user edits message from top of the chat and press "New message" button, at that time it will scroll back to latest chat but chat compose box does not show i.e. chat compose box will disappear.

What is the root cause of that problem?

Whenever we edit any message from the top of the chat at that time composer gets hidden. Meanwhile when we tap "New message" at that time we will scroll to the bottom of chat, but we do not take care to show composer by assuming that composer is already visible. So in this situation composer remain hidden.

App/src/pages/home/report/ReportActionsView.js

Lines 297 to 300 in 94057ba

	scrollToBottomAndMarkReportAsRead() {
	ReportScrollManager.scrollToBottom();
	Report.readNewestAction(this.props.report.reportID);
	}

What changes do you think we should make in order to solve the problem?

To solve this we have to call toggle report action compose view from scrollToBottomAndMarkReportAsRead() function within src/pages/home/report/ReportActionsView.js file as shown under:

 scrollToBottomAndMarkReportAsRead() { 
    toggleReportActionComposeView(true, this.props.isSmallScreenWidth);
    ....
 } 

So using this solution it will scroll down to new message and show compose box (instead of disappear) as shown in result video and also solve the scroll bar showing on the left issue.

With this solution it will not automatically take you out from edit mode. It is different issue and I think it should be handled separately.

What alternative solutions did you explore? (Optional)

None

Result iOS

iOS.mp4

[MelvinBot]

📣 @PrashantMangukiya! 📣

Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
2. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
3. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[MelvinBot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[parasharrajat]

It seems like we have some discussion on the Slack thread which I need to go through. I will update here based on it tomorrow.

[sonialiap]

@parasharrajat do we have an update for this issue?

[parasharrajat]

Sorry not yet. I will be able to pick it up tomorrow. Basically, I am planning on deciding the next steps here not just summarizing the slack thread.

[michaelhaxhiu]

Seems like @s77rt opened a GH react-native-community/discussions-and-proposals#640 and @parasharrajat needs to review. Can we aim to do that in the next 1-2 days?

[sonialiap]

Not overdue

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[melvin-bot]

@chiragsalian, @sonialiap, @parasharrajat Whoops! This issue is 2 days overdue. Let's get this updated quick!

[sonialiap]

@parasharrajat seems like we're waiting on your review for this issue, any updates?

[melvin-bot]

@chiragsalian, @sonialiap, @parasharrajat Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[parasharrajat]

There is no PR to review yet. I reviewed the proposal but there are no updates on it. I am going to review this issue's state and proceed which looks like the best thing to do about it.

I am done for today but this will happen in 1-2 days (excluding weekends).

[sonialiap]

Sounds good, thanks for the update

[melvin-bot]

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[sonialiap]

I cannot reproduce anymore either. Will check in slack if the reporter can reproduce this. It's possible it was fixed by something else along the way.

Closing for now, will reopen if I get a comment in slack that the issue can still be reproduced