bettybop68 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 1 forks source link

The notification format sent when a file has been downloaded through FToHTTP is bad-formed #134

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Start a 1-To-1 Chat between 2 users
2.Users exchange some messages through MSRP
3.A user send a file through FToHTTP
4.The link to donwload the file is sent through the MSRP channel of the 1-To-1 
session
5.The user accepts the file trasnfer

What is the expected output? 
The user sends a displayed notification.
It must content : 
<datetime>2013-08-07T08:47:21.000Z</datetime>
<display-notification><status><displayed/></status></display-notification>
</imdn>

What do you see instead?
The user send a bad formed displayed notification.
It is formed like : 
<datetime>2013-08-07T08:47:46.000Z</datetime>
<processing-notification><status><display/></status></processing-notification>
</imdn>

What version of the product are you using? On what operating system?
2.5.7

Please provide any additional information below.
In attachement, a network trace. The SIP MESSAGE request with a bad formed 
notification content is available in paquet 2450.

Original issue reported on code.google.com by brochard...@gmail.com on 9 Aug 2013 at 8:30

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by jmauffret@gmail.com on 19 Aug 2013 at 12:05

GoogleCodeExporter commented 8 years ago
Correction under validation

Original comment by jmauffret@gmail.com on 27 Aug 2013 at 8:19

GoogleCodeExporter commented 8 years ago
Fixed in v2.5.8

Original comment by jmauffret@gmail.com on 28 Aug 2013 at 1:49