Re: [Opensync-users] syncml-obex-client fails to synchronize calendar

[Robert H. <ope...@hu...>]

> At the moment, I filter all objects but the one type I want to sync
> (and "data", as it would fail horribly if I filtered this type).
>
> I have problems syncing the events, though:
> "Mapping Write Error: content type was not configured" messages over and
> over. I'm looking into this at the moment. As soon as it works, I can try
> if syncing both contacts and events at the same time works.

Okay, I found this one. Opensync was receiving a wrong dsession, indicated by 
the message (on the console):
  received contact dsession

I do not understand the code well enough to fix this, but it's caused by both 
contact_db and calendar_db having the same content: "addressbook". I renamed 
the contact_db to something else (no problem as I'm not syncing it at the 
moment), and now it picks the correct dsession:
  received event dsession

The trace files (for the case when contact_db and calendar_db were the same) 
show that it probably only compares the locations, not checking if that 
location really belongs to the Calendar.

>>>>>>>  _event_callback(0x80639b0, 1, 0x8067118, (nil), (nil), (nil), 
0x805f880)
	>>>>>>>  smlManagerDispatchCommand(0x805f880, 0x80639b0, 0x8067118, 
0xb69ceee8)
		>>>>>>>  smlManagerObjectFind(0x805f880, 0x80639b0, 0x8067118)
			>>>>>>>  smlLocationCompare((nil)(null), 0x805fa58(addressbook), (nil)
(null), 0x80636c8(addressbook)
				>>>>>>>  normalizeUrl(addressbook)
				<<<<<<<  normalizeUrl: addressbook
				>>>>>>>  normalizeUrl(addressbook)
				<<<<<<<  normalizeUrl: addressbook
				Comparing addressbook and addressbook
			<<<<<<<  smlLocationCompare: 1
			>>>>>>>  smlLocationCompare((nil)(null), (nil)(null), (nil)(null), 
0x8061960(Calendar))
			<<<<<<<  smlLocationCompare: No object given: TRUE
		<<<<<<<  smlManagerObjectFind: FOUND: 0x805fac0


Note the line "smlLocationCompare((nil)(null), (nil)(null), (nil)(null), 
0x8061960(Calendar))". It's probably trying to make sure that it's the 
calendar's location, but it's not too successful in doing that...

Using the workaround I described above, I was able to sync a dozen events or 
so with the phone. Until the sync hang once again, with the trace showing:
				<--- ERROR --- smlWbxmlConvertTo: Parsing of XML Document Failed
			<--- ERROR --- smlWbxmlAssemblerCheckSize: Parsing of XML Document Failed
		<--- ERROR --- smlAssemblerCheckSize: Parsing of XML Document Failed
	<--- ERROR --- smlAssemblerStartCommand: Parsing of XML Document Failed
<--- ERROR --- _smlSessionStartCommandInternal: Parsing of XML Document Failed

Debugging in progress... ;-)

Sincerely,
  Robert