Ticket #131 (reopened defect)

Opened 7 months ago

Last modified 1 week ago

SyncML Connection Issues (possible wbxml conversion issues)

Reported by: jaymzh Assigned to: dgollub
Priority: high Component: libsyncml
Version: 0.4.6 Severity: normal
Keywords: Cc: phil@ipom.com

Description (Last modified by felixmoeller)

Filing this bug here at the request of Daniel Gollub. I have a Nokia 6555 that I'm having trouble talking to with SyncML. I can connect, but somewhere in the wbxml process, things get confused: 

[phil@rider libsyncml-0.4.6]$ sudo ./tools/syncml-obex-client -u 0
--identifier "PC Suite Data Sync" --wbxml  --sync text/x-vcard Contacts
connection with device succeeded
Received an Alert for the DS Server at Contacts: Type: 201, Last 0, Next 92
Just received a new session with ID 1
Session 1 reported final. flushing

Errors from SyncML tracing show: 

Thread3081673616-18718.log:[1201597169.902212]
    <--- ERROR --- smlXmlDevInfParse: Wrong name
Thread3081673616-18718.log:[1201597169.902246]
    <--- ERROR --- smlDevInfParse: Wrong name
Thread3081673616-18718.log:[1201597169.902275]
    <--- ERROR --- _recv_devinf: Wrong name
Thread3081673616-18718.log:[1201597169.905015]
    <--- ERROR --- smlDevInfGetCTCap - failed
Thread3081673616-18718.log:[1201597169.905102]
    <--- ERROR --- smlDevInfGetCTCap - failed

Full trace logs are attached.

Attachments

6555-2.tar.bz2 (115.1 kB) - added by jaymzh on 01/29/08 18:17:23.
syncml logs for 6555.
6555-3.tar.bz2 (171.3 kB) - added by jaymzh on 01/31/08 19:55:01.
Newer logs.

Change History

01/29/08 18:17:23 changed by jaymzh

  • attachment 6555-2.tar.bz2 added.

syncml logs for 6555.

01/29/08 18:54:24 changed by dgollub

  • status changed from new to closed.
  • resolution set to fixed.

Issue turned out to be a wbxml2 issue. This is very likely fixed with wbxml2 0.4.2 + SVN42

For the record:

How to validate the issue

#1 Check the recieved-*.xml files for "<unknown>" XML nodes. #2 If so, check your version of wbxml2 #3 Version wbxml2 0.4.2 and less are affected by this issue #4 Upgrade wbxml2 0.4.2 at least to SVN42

libwbxml: http://libwbxml.aymerick.com/

01/31/08 19:54:24 changed by jaymzh

  • status changed from closed to reopened.
  • resolution deleted.

That seemed to be only *part* of the issue. With the latest wbxml libraries, the conversion to XML works, but I still get similar symptoms. The 'grep -i error *' is below and the full logs are attached.

- Phil

Thread3081366416-3109.log:[1201628210.422225]

<--- ERROR --- _smlXmlDevInfDataStoreParseCTCap12Property: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.422255]

<--- ERROR --- _smlXmlDevInfDataStoreParseCTCap12: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.422401]

<--- ERROR --- _smlXmlDevInfDataStoreParse: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.422553]

<--- ERROR --- smlXmlDevInfParse: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.422587]

<--- ERROR --- smlDevInfParse: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.422618]

<--- ERROR --- _recv_devinf: Unknown CTCapType for Property: ParamName?

Thread3081366416-3109.log:[1201628210.425341]

<--- ERROR --- smlDevInfGetCTCap - failed

Thread3081366416-3109.log:[1201628210.425428]

<--- ERROR --- smlDevInfGetCTCap - failed

01/31/08 19:55:01 changed by jaymzh

  • attachment 6555-3.tar.bz2 added.

Newer logs.

01/31/08 21:45:20 changed by dgollub

Result of WBXML to XML conversion is invalid.

<Property><ParamName/?></Property> isn't allowed. Inteded child node would be <ValEnum?> instead of <ParamName?> sounds like an wbxml2 issue.

01/31/08 22:22:54 changed by dgollub 

WBXML Parser> (488) Parsing content: '0x57'
WBXML Parser> (488) Parsing element
WBXML Parser> (488) Parsing stag
WBXML Parser> (488) Token: 0x17
WBXML Parser> <ParamName>

Token ID for ValEnum? is 0x23 ... not 0x17. Not quite sure if's an issue of libwbxml2 or of your mobile. Have to take a more closer look inside of libwbxml2.

02/01/08 06:52:39 changed by jaymzh

Revision r347 seems to work (as long as I use the latest SVN of libwbxml2) - but looking at the diff you added support for <ParamName?>, which apparently isn't valid. Hmmm. Well, r347 is definitely at least a work around.

Let me know what I can do to help - as always, I'm happy to test patches.

02/20/08 03:12:02 changed by jaymzh

Any progress on a more permanent solution? Any patches I should test?

02/20/08 03:12:49 changed by jaymzh

  • cc set to phil@ipom.com.

Adding myself to the CC.

08/12/08 14:11:03 changed by felixmoeller

  • description changed.