On Sa, 2010-10-30 at 09:26 +0100, Giancarlo wrote:
> Giancarlo <ia...@...> writes:
>
> >
> > Patrick Ohly <patrick.o...@...> writes:
> >
> > > > cannot sync my phones (nokia E61 and nokia 6220 classic) because I get
> > an error
> > > > 412.
> > > > When this happens I must refresh-from-server and afterward the nokia
> > > > 6220
> > > > classic works correcly.
> > >
> > > Again a log file will be needed.
> > >
> > This is feasable: my calendar is not that sensitive... I never meet people
> > from Mafia, even if I'm from Sicily. So never mind even if someone taps my
> > email...
> >
>
> Hi Patrick,
> I'm sending you privately the log of my synchronization with Nokia6620
> Classic.
>
> I sync'ed using the GUI and asking only a calendar (regular: two-way) sync.
> Before sync'ing, I made a change to two (or three?) entries in the calendar on
> the server side (through Evolution), in order to replicate the error. As
> expected, the error 412 appeared and no sync was performed on the phone.
Can you replicate it with any kind of update or only with some of them?
There wasn't anything particularly exotic about the one which triggered
the 412 error in your log.
The phone is sent two properties which are optional in vCalendar 1.0,
UID and SEQUENCE. Perhaps it doesn't like them. Can you try again after
making the following changes?
1. copy /usr/share/syncevolution/xml/datatypes/11calendar-profile.xml into
your home directory as
~/.config/syncevolution-xml/datatypes/11calendar-profile.xml
2. Find '<property name="SEQUENCE"' in it.
3. Add onlyformode="standard" (similar to "GEO" right underneath
it).
4. Do the same for UID.
5. Repeat your experiment.
If it still fails, then please verify that UID and SEQUENCE number were
not included in the BEGIN:VCALENDAR that was "Generated".
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
