My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2378: Unsent messages are lost if trying to re-open them after starting to write another message
3 people starred this issue and may be notified of changes. Back to list
Status:  Obsolete
Owner:  ----
Closed:  Jun 2013


Sign in to add a comment
 
Reported by luke.hutch, Apr 6, 2009
Assuming that you're somewhere without signal, so that SMS message will not
be sent:

1. Write and send message 1
2. Start writing message 2 but don't send it
3. When the "message not sent" notification pops up, select it to
view/resent message
4. It takes you back to the message editor, but since you have already
started writing message 2, the text from message 1 is not inserted into the
editor field, and message 1 is lost.

Additionally it is not possible to manually start the re-sending of unsent
messages by clicking on them, you have to go back to "all threads" and use
the menu item "Undelivered messages", or use the statusbar icon.  The
actual message doesn't seem to be stored in the thread in an unsent state.
 Based on the above bug, it seems like the data model assumptions are
responsible for the UI brokenness.  It would be nice if drafts and unsent
messages were just stored in the thread, and could be switched to / edited
at will without causing data loss to other items.
Aug 26, 2009
#1 jbq+legacy@google.com
(No comment was entered for this change.)
Labels: Component-Applications
Aug 31, 2009
#2 jlapenna@google.com
(No comment was entered for this change.)
Labels: Subcomponent-Messaging
Jun 23, 2013
#3 jbq@android.com
Based on its date, this issue was originally reported before Android 4.x. Because of the many changes that existed in Android 4.x compared to previous versions, it's very likely that this issue doesn't exist in recent versions of Android like 4.2.2 or newer. Because of the high likelihood that this issue is obsolete, it is getting closed automatically by a script, without a human looking at it in detail. If the issue still exists on a Nexus 4 or Nexus 7 running Android 4.2.2 and is not related to Google applications, please open a new report accordingly.

Status: Obsolete
Sign in to add a comment

Powered by Google Project Hosting