[PAID] [$500] Members - Invite message doesn't remain when User navigate back to Invite members page

[lanitochka17]

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. Create new Workspace
2. Navigate to Members
3. Tap on Invite button
4. Invite few users
5. Tap Next
6. Edit the Invite message and put new message
7. Navigate back to Invite Members page
8. Tap Next button

Expected Result:

Invite message should remain when User come back to final Invite page

Actual Result:

Invite message doesn't remain when User navigate back to Invite members page

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.72-6

Reproducible in staging?: Yes

Reproducible in production?: Yes

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

Bug6208025_az_recorder_20230920_223129.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0111f805abe8b69c9a
• Upwork Job ID: 1714431162859646976
• Last Price Increase: 2023-11-07

[melvin-bot]

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

[melvin-bot]

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

[neonbhai]

Proposal

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

Users lose written invite message when they accidentally trigger back navigation

What is the root cause of that problem?

We are missing the draft saving logic on the Input Field

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

We should pass shouldSaveDraft to the TextInput here:

App/src/pages/workspace/WorkspaceInviteMessagePage.js

Lines 213 to 227 in 94c07ea

	<TextInput
	ref={(el) => (this.welcomeMessageInputRef = el)}
	accessibilityRole={CONST.ACCESSIBILITY_ROLE.TEXT}
	inputID="welcomeMessage"
	label={this.props.translate('workspace.inviteMessage.personalMessagePrompt')}
	accessibilityLabel={this.props.translate('workspace.inviteMessage.personalMessagePrompt')}
	autoCompleteType="off"
	autoCorrect={false}
	autoGrowHeight
	textAlignVertical="top"
	containerStyles={[styles.autoGrowHeightMultilineInput]}
	defaultValue={this.state.welcomeNote}
	value={this.state.welcomeNote}
	onChangeText={(text) => this.setState({welcomeNote: text})}
	/>

What alternative solutions did you explore? (Optional)

xx

[alexpensify]

I'm unable to test right now due to the site issues and will be traveling for work later today. If I get plane wifi, then I'll try to test either tonight or this weekend.

[alexpensify]

I'm back online and will try to test soon.

[alexpensify]

Not overdue, CM tasks are a higher priority right now. I'll test this one soon.

[alexpensify]

I confirmed this experience but I'm asking in the Open Source room to verify if the lack of stickyness is on purpose.

Here: https://expensify.slack.com/archives/C01GTK53T8Q/p1695969085525799