|
From: Daniel G. <dg...@su...> - 2007-12-29 22:33:18
|
On Saturday 29 December 2007 14:06:32 li...@ba... wrote:
> I've used the latest version of libsyncml and tried the syncml-obex-client
> tool for testing. This showed the same behavior as opensync. Therefore I
> assume it might be a problem in libsyncml. In the following the debug
> output, with a self-compiled open-obex library.
I just had a quick look on the syncml log dumps. I guess following SyncML
message generated by libsyncml is wrong (sent-1.xml):
<SyncBody>
<Status>
...
<SourceRef>Sony Ericss</SourceRef>
<TargetRef>IMEI:xxxxxxxxxxxxxx</TargetRef>
....
</Status>
....
</SyncBody>
Actually your identifier string should be in that context the <TargetRef/>,
and the IMEI string in <SourceRef/>. Since the Status refers from a SyncML
command which got emitted by the mobile. And for the mobile the Target is
libsyncml ...
I'll review the commits to see when this bug got introduced... not quite sure
if r263 is affected or not.
best regards,
Daniel
|