calendar only synced from mobile to owncloud not reverse

[sideshowbob84]

Hi,
thanks for updating your nice piece of software.
I tested it with owncloud 4.5.4 and my webos phone and tablet. The calendar items are not getting duplicated anymore (nice!), but now i have the problem, that items created in owncloud are not synced to my phone/tablet (the other way no problems so far). The funny thing is, that (i have android dualboot on the touchpad) android 4 does not have this problem. So this issue is maybe a problem of only webos or the z-push backend. But i am not skilled enough to decide this, so i opened this issue here in the hope that someone is able to tell me.
I pasted a log at https://gist.github.com/4318356 which was created while i made one entry on the phone (called "frommobile") and another on owncloud (called "fromoc")
Thanks a lot
sideshowbob

P.S. I already tried all possible combinations of define('PROVISIONING', true/false) and define('LOOSE_PROVISIONING', true/false);

[gza]

Hi, I do not have a webos device to do testings, sorry.
Did it already worked ?

BTW, I saw in forums that webos should be bugged with AS2.5 protocol.
Could you try to add this at the end of backend/occombined/occombined.php
juste before last "}"

/**
 * Indicates which AS version is supported by the backend.
 *
 * @access public
 * @return string       AS version constant
 */
public function GetSupportedASVersion() {
    return ZPush::ASV_14;
}

please keep us in touch.

Guillaume

[sideshowbob84]

Hi, yes it already worked. But i had the duplicated entry issue. Thank you for your possible fix. I will test it tomorrow and will report here!

[gza]

hmmm, if it does already worked ... with which commit ?

[gza]

did you restarted from scratch your installation while upgrading ?
-> unconfigure device
-> rm /var/lib/z-push/*
-> restart apache
-> reconfigure device

Is it recurring events ? I did have this kind of problem while coding...

[sideshowbob84]

Hi,
thanks for your help and your active development. I always restartet from scratch and i am testing with a very simple (not recurring) event.

I first tested your provided fix against the latest commit. That didn't change anything. Afterwards i tested every commit made in the last few days starting at e58.. [update iCalcreator, add rtfclass for tests (not enabled)]. The problems starting to appear only from the third last commit 25e1... [some timeZone rework and hope fixes :)]. So the problem lies not in the merge of z-push 2.0.6. When i am on the commit 4624.. [updated upstream z-push version to 2.0.6-1616] the duplicated items error disappears. I only have the problem, that items created in owncloud are synced with a difference from one hour more to my device. So a 10-11 o'clock item created in owncloud is an 11-12 o'clock event (my timezone is UTC+1).
When i switch to 25e1... [some timeZone rework and hope fixes :)] i have the problems described in the starting post. So from phone to owncloud no problem but from owncloud to phone nothing is synced.
(maybe another issue or not: in every newer commit items from the phone are only half correctly synced to owncloud. By that i mean that the time displayed in owncloud calendar view is correct, but if i view the items details by clicking on it in owncloud, the time displayed is one hour less).
Thanks again and tell me if i can test anything else or could be of help in another way!

[sideshowbob84]

Hi,
i looked a little bit into the z-push.log. I didn't find anything (which doesn't mean anything, because i am not good at that). The only thing that looked a little bit suspicious were the different beginnings of the timezone base64 strings.

for an item created on the mobile:
[timezone] => xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAEAAIAAAAAAAAAxP///w==

for an item created on owncloud:
[timezone] => ////xAAoAEcATQBUACsAMAAxADoAMAAwACkAIABBAG0AcwB0AGUAcgBkAGEAbQAsACAAQgBlAHIAbABpAG4ALAAgAEIAAAoABQAAAAMAAAAAAAAAAAAAAAAoAEcATQBUACsAMAAxADoAMAAwACkAIABBAG0AcwB0AGUAcgBkAGEAbQAsACAAQgBlAHIAbABpAG4ALAAgAEIAAAMABQAAAAIAAAAAAAAA////xA==

I don't know if there is a problem or not. But that was the only thing i noticed.

[gza]

Thanks, I think you put me in the right way and I probably found the problem. But I don't have much time today to test and commit it.
could you try this patch ? https://gist.github.com/4328134

[sideshowbob84]

Thanks a lot, but i have tested the fix this evening and couldn't notice any changes.... But it is difficult to tell if the problem lies in webos or not (i hope not). Is there anything else that i can do?

[gza]

any change on the timezone field when created from owncloud ?

[ghost]

The above log with timezone field looks exactly as in my tests with Z-Push original and Zarafa Backend, described here: http://z-push.sourceforge.net/phpbb/viewtopic.php?f=7&t=2137. But as manfred told me, my problem is a Zarafa Bug. The Zarafa Ticket is here: https://jira.zarafa.com/browse/ZCP-10711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

But i cant use Zarafa at this time. I was using it only in a VMWare Image and this isnt possible now. So im in search for a alternative solution via CalDAV / CardDAV and IMAP Backend. Thats the reason, i look n to your Project (and some others) :-)

[sideshowbob84]

Hi, new log can be found here: https://gist.github.com/4335482
extracts from new log:

from mobile:
[timezone] => xP///wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAoAAAAEAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAAEAAIAAAAAAAAAxP///w==

from owncloud
[timezone] => ////xAAoAEcATQBUACsAMAAxADoAMAAwACkAIABBAG0AcwB0AGUAcgBkAGEAbQAsACAAQgBlAHIAbABpAG4ALAAgAEIAAAoABQAAAAMAAAAAAAAAAAAAAAAoAEcATQBUACsAMAAxADoAMAAwACkAIABBAG0AcwB0AGUAcgBkAGEAbQAsACAAQgBlAHIAbABpAG4ALAAgAEIAAAMABQAAAAIAAAAAAAAA////xA==

I can see no changes sorry.

[sideshowbob84]

Hi, is there anything else that i can do to help?
What would interest me is, if this a real bug but android for example is not bothered by it, or is it in fact no bug and the problem lies in webos? Can someone help me to determine this? Because if it is a real bug i could wait for a fix, but if the problem lies deeper for example in webos i think i should look for different solution.
Thanks a lot and a happy new year!