Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IAM-WL - Sending a MMS with no attachment improperly populates the conversation thread #2

Open
tarasklimenko opened this issue Jan 31, 2014 · 3 comments
Assignees
Labels

Comments

@tarasklimenko
Copy link

Upon sending a new message with the Address, Subject & Text fields populated, the conversation thread is populated with an invalid message. Message is titled "undefined" (see attached). The message is sent & received properly.

Expected: Sending a message, regardless of the populated fields (must include address of course), should properly populate the conversation thread with the details provided.

Actual: After sending the MMS without an image attachment, the conversation thread is left with an "undefined" message (see attached).

Repro:

  1. Hit "New" message
  2. Populate the Address, Subject & Text fields without adding an attachment
  3. Notice "Message Sent" notification appears
  4. Notice message is received properly including all populated fields
  5. Notice the conversation thread is left with an "undefined" message with a blocked "download" button. ( See attached).

screenshot_2014-01-30-17-04-54 1

@ghost ghost assigned mattcobb Jan 31, 2014
@tarasklimenko
Copy link
Author

Testing the new build, MMS without an attachment are shown improperly like so:

image

image

@rajiv614
Copy link
Contributor

rajiv614 commented Feb 4, 2014

Screenshot 1
The spec for the Iam Sample Application required the subject to be shown for mms on the messagelist page. Is that the subject you set for that particular mms?
Screenshot 2
In order for this fix to come into effect you must do a 1 time log out and then log back in . Can you confirm if this issue still exists after trying that?

@tarasklimenko
Copy link
Author

Screenshot 1 is working as expected, it's screenshot 2 that is showing the improper behavior. But I am unable to reproduce this anymore. Current behavior is described in issue #17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants