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:
- Navigate to a conversation
- Write something in the compose box
- Log out of the account.
- Log in again with the same account
- Navigate to the same conversation
Expected Result:
The previous drafted message should be displayed even if the user logged out and back in
Actual Result:
Drafted message is not saved if the user logs out
Workaround:
Save the drafted message elsewhere if the user is logging out.
Platform:
Where is this issue occurring?
- Web
- iOS
- Android
- Desktop App
- Mobile Web
Version Number: 1.1.2-0
Reproducible in staging?: yes
Reproducible in production?: yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1632412938049600
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @chuckdries
Issue Owner
Current Issue Owner: @chuckdries
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:
Expected Result:
The previous drafted message should be displayed even if the user logged out and back in
Actual Result:
Drafted message is not saved if the user logs out
Workaround:
Save the drafted message elsewhere if the user is logging out.
Platform:
Where is this issue occurring?
Version Number: 1.1.2-0
Reproducible in staging?: yes
Reproducible in production?: yes
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1632412938049600
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @chuckdries
Issue Owner
Current Issue Owner: @chuckdries