Ticket #684 (assigned defect)

Opened 6 months ago

Last modified 3 weeks ago

element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

Reported by: jas Assigned to: cstender (accepted)
Priority: high Milestone: 0.38
Component: Plugin: vformat Version: 0.36
Severity: normal Keywords:
Cc:

Description

Hi! I get this error when syncing with my nokia e51:

element Count: Schemas validity error : Element 'Count': This element is not expected. Expected is ( Frequency ).

The vevent is (sensitive information modified, but nothing else), from the file-sync local storage: 

BEGIN:VCALENDAR
PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN
VERSION:2.0
BEGIN:VEVENT
CLASS:PRIVATE
DTEND:20060613T220000Z
DTSTART:20060613T220000Z
LAST-MODIFIED:20080207T145019Z
PRIORITY:0
RRULE:COUNT=0;INTERVAL=1
SEQUENCE:0
SUMMARY:Foo
UID:07022008145019137375-0
END:VEVENT
END:VCALENDAR

See also discussion at: http://thread.gmane.org/gmane.comp.misc.opensync.user/2453/focus=2455

Note that I don't get the same vevent card from the phone if I sync with 'vevent10' instead of 'vevent20'. Is this a problem in the phone? If I sync using vevent20 type in the syncml-obex-client configuration, I get the following vevent card (for same instance): 

BEGIN:VCALENDAR

PRODID:-//OpenSync//NONSGML OpenSync vformat 0.3//EN

VERSION:2.0

BEGIN:VEVENT

CLASS:PRIVATE

DTEND:20060613T220000Z

DTSTART:20060613T220000Z

LAST-MODIFIED:20080207T145019Z

PRIORITY:0

RRULE:FREQ=YEARLY;UNTIL=21000613T0000-1Z;INTERVAL=1;BYMONTH=6

SEQUENCE:0

SUMMARY:Foo
UID:07022008145019137375-0

END:VEVENT

END:VCALENDAR

Thanks, Simon

Change History

02/13/08 14:59:04 changed by jas

Sorry, I mixed up 'vevent20' vs 'vevent10' there: the first vevent card (the incorrect one) was synced using vevent20 and the "correct" card was synced using vevent10.

I was also able to retrieve the "real" vevent card as returned by syncml-obex-client --slow-sync instead, and it is (regardless of whether it was synced with text/calendar or text/x-vcalendar): 

BEGIN:VCALENDAR
VERSION:1.0
TZ:+01
DAYLIGHT:TRUE;+02;20060326T010000Z;20061029T010000Z;;
DAYLIGHT:TRUE;+02;20080330T010000Z;20081026T010000Z;;
DAYLIGHT:TRUE;+02;20090329T010000Z;20091025T010000Z;;
DAYLIGHT:TRUE;+02;20100328T010000Z;20101031T010000Z;;
DAYLIGHT:TRUE;+02;20110327T010000Z;20111030T010000Z;;
DAYLIGHT:TRUE;+02;20120325T010000Z;20121028T010000Z;;
BEGIN:VEVENT
UID:07022008145019137375-0
SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:Foo
DTSTART:20060613T220000Z
DTEND:20060613T220000Z
X-EPOCAGENDAENTRYTYPE:APPOINTMENT
CLASS:PRIVATE
SEQUENCE:0
X-METHOD:NONE
RRULE:YM1 6 21000613T000000
LAST-MODIFIED:20080207T145019Z
PRIORITY:0
X-SYMBIAN-LUID:30
END:VEVENT
END:VCALENDAR

Thanks, Simon

02/13/08 17:26:25 changed by felixmoeller

This seems the same as bug #678 ...

02/13/08 17:35:31 changed by jas

Yeah, they look the same. At least we now know that this arise in rather different environments.

02/14/08 13:07:03 changed by cstender

  • status changed from new to assigned.
  • milestone set to OpenSync 0.40.

02/25/08 15:17:36 changed by cstender

  • priority changed from normal to high.

Can you please provide OpenSyncs? trace files? I can't find the error with vformat.

07/30/08 18:13:31 changed by tuju

  • milestone changed from 0.40 to 0.38.