Still cannot get display image of some account

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Connect the example client to WLM service
2. Open the conversation dialog for cecilia_carron@hotmail.com
3. Use the WLM to do the same thing

What is the expected output? What do you see instead?

The display picture can be seen on both example client and official WLM
Only official WLM can see the display image.

Please use labels and text to provide additional information.

Please look at the trace log.

Original issue reported on code.google.com by freezing...@gmail.com on 15 Apr 2011 at 5:53

Attachments:

• cannot_get_displayimage.txt

[GoogleCodeExporter]

It seems the first incoming message is "data preperation" and the next is "BYE 
SLP"...
I don't think so it is msnpsharp related issue.

We must know "Why remote contact sends the bye message after data preparaion?".

Here is the packets:

P2PSession: 1609349633 invitation sent with SYN+RAK op and received 
RemoteBaseIdentifier is: 2750832003
P2PHandler: Received P2PMessage from 1:SDGBridge
[P2PMessage]
[P2Pv2Header]
HeaderLength        : 8 (8)
OperationCode       : 0 (0)
MessageSize         : 1ad (429)
Identifier          : a3f65d83 (2750832003)
AckIdentifier       : 0 (0)
NakIdentifier       : 0 (0)
Header TLVs  (0)    : 
 Data HeaderLength  : 8 (8)
 TFCombination      : First (1)
 PackageNumber      : 0 (0)
 SessionId          : 0 (0)
 DataRemaining      : 0 (0)
 DataPacket TLVs (0): 
FOOTER              : 0 (0)
DATA                : MSNSLP/1.0 200 OK
Call-ID: {BB1FB970-C49A-4477-A134-8DD68E5E6888}
Content-Length: 26
Content-Type: application/x-msnmsgr-sessionreqbody
CSeq: 1
From: 
<msnmsgr:cecilia_carron@hotmail.com;{908b2729-964c-4204-997b-0798d7238456}>
Max-Forwards: 0
To: <msnmsgr:testmsnpsharp@live.cn;{0fd01c06-c60b-4130-b3be-88e068dd8f78}>
Via: MSNSLP/1.0/TLP;branch={12799B82-E9C1-4910-AE4E-F474F0EDBAC5}

SessionID: 1609349633

P2PSession: P2PSession 1609349633 active
ObjectTransfer: Transfer started
P2PHandler: Received P2PMessage from 1:SDGBridge
[P2PMessage]
[P2Pv2Header]
HeaderLength        : 8 (8)
OperationCode       : 0 (0)
MessageSize         : c (12)
Identifier          : a3f65f30 (2750832432)
AckIdentifier       : 0 (0)
NakIdentifier       : 0 (0)
Header TLVs  (0)    : 
 Data HeaderLength  : 8 (8)
 TFCombination      : First (1)
 PackageNumber      : 0 (0)
 SessionId          : 5fecba01 (1609349633)
 DataRemaining      : 0 (0)
 DataPacket TLVs (0): 
FOOTER              : 0 (0)
DATA                : Binary data: 4 bytes

ObjectTransfer: Received 4 / 22957
P2PHandler: Received P2PMessage from 1:SDGBridge
[P2PMessage]
[P2Pv2Header]
HeaderLength        : 8 (8)
OperationCode       : 0 (0)
MessageSize         : 1f1 (497)
Identifier          : a3f65f3c (2750832444)
AckIdentifier       : 0 (0)
NakIdentifier       : 0 (0)
Header TLVs  (0)    : 
 Data HeaderLength  : 8 (8)
 TFCombination      : First (1)
 PackageNumber      : 1 (1)
 SessionId          : 0 (0)
 DataRemaining      : 0 (0)
 DataPacket TLVs (0): 
FOOTER              : 0 (0)
DATA                : BYE 
MSNMSGR:testmsnpsharp@live.cn;{0fd01c06-c60b-4130-b3be-88e068dd8f78} MSNSLP/1.0
Call-ID: {BB1FB970-C49A-4477-A134-8DD68E5E6888}
Content-Length: 26
Content-Type: application/x-msnmsgr-sessionclosebody
CSeq: 0
From: 
<msnmsgr:cecilia_carron@hotmail.com;{908b2729-964c-4204-997b-0798d7238456}>
Max-Forwards: 0
To: <msnmsgr:testmsnpsharp@live.cn;{0fd01c06-c60b-4130-b3be-88e068dd8f78}>
Via: MSNSLP/1.0/TLP;branch={D34FD0B1-32C0-4738-857E-EE9023216DC1}

SessionID: 1609349633

Original comment by hepha...@gmail.com on 15 Apr 2011 at 7:40

[GoogleCodeExporter]

Sorry, I haven't got time to look into detail, maybe the sequence number is not 
correct or something. Here I attach a log from the 3.1 stable, which can get 
the image.

Original comment by freezing...@gmail.com on 16 Apr 2011 at 6:09

Attachments:

• 31_stable_can_get_displayimage.txt

[GoogleCodeExporter]

I got the problem, it's one of the old bug I've fixed in 3.0. The base64 of 
MSNObject encoding is wrong. Let me check why the heck it happens again.

Original comment by freezing...@gmail.com on 16 Apr 2011 at 6:22

[GoogleCodeExporter]

Please merge all these fixes to trunk.

Original comment by freezing...@gmail.com on 16 Apr 2011 at 7:12

• Changed state: Fixed

[GoogleCodeExporter]

BTW, there are still several issues and updates here, I need time to verify 
them.

Original comment by freezing...@gmail.com on 16 Apr 2011 at 7:54

[GoogleCodeExporter]

MSNObject.cs:387

This line throws XmlException.

XmlNode node = xmlDocument.ReadNode(xmlReader);

Stack trace:
System.Xml.XmlException: '.' (invalid hex 0x00), invalid char. Line 1, col 133.
   konum: System.Xml.XmlTextReaderImpl.Throw(Exception e)
   konum: System.Xml.XmlTextReaderImpl.ThrowInvalidChar(Int32 pos, Char invChar)
   konum: System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace()
   konum: System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   konum: System.Xml.XmlLoader.ReadCurrentNode(XmlDocument doc, XmlReader reader)
   konum: System.Xml.XmlDocument.ReadNode(XmlReader reader)

Original comment by hepha...@gmail.com on 16 Apr 2011 at 7:10

• Changed state: Accepted

[GoogleCodeExporter]

What is the context passed into the function? It's must be null or an empty 
string.

Original comment by freezing...@gmail.com on 16 Apr 2011 at 8:10

[GoogleCodeExporter]

Original comment by freezing...@gmail.com on 16 Apr 2011 at 8:13

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by hepha...@gmail.com on 19 Apr 2011 at 7:49

• Added labels: Milestone-Release4.0.0