"Local storage error – Empty result from content provider"
No “caused by”. I have to head off now, but will send you an anonymised version of the full output soon.
@rfc2822 Just sent you an anonymised version of the full debug output.
I couldn’t reproduce the problem with Android 8.1 (emulator) and an iCalendar which I have created from your event data. However, I noticed that it seems to contain
RRULE:FREQ=DAILY;BYDAY=MO,TU,WE,TH,FR– maybe this unlimited number of instances causes problems on your device, for instance because there’s no more memory to store the instance data? This could cause the Android calendar storage (which does
RRULEexpansion) to crash, which would then cause an empty response to DAVdroid.
Does it work when you use no or another
RRULEwith a limited number of instances? How much (disk) memory do you have on your device? What happens if you delete this event – does the problem occur for other events, too? Do you have another Android device where you could try synchronization? Is there any other way to reproduce the problem, so that I can get an idea?
Just created an event series with no end date in a different calendar. Syncing without problems.
My gut feeling is that it’s more related to the fact that I was invited to the event by someone else, i.e. someone else actually owns the event series.
Also I’m not sure whether emulating using Android 8.1 helps, since it’s working fine on my Samsung device, not on my Huawei device though (as mentioned at the beginning of this thread).
@6042114fa0 If you find a way to reproduce the problem, please let me know. I’d have to reproduce the problem in order to debug it. Unfortunately, Android components which don’t return anything to DAVdroid are usually difficult to debug…
Sure, but that would require a Zimbra server where I have more than one account so I can play around. I’m afraid I don’t have such a server.
This might be related: https://forum.xda-developers.com/huawei-p20-pro/help/p20-pro-problems-exchange-sync-t3775032
@6042114fa0 You could also try to clear the calendar storage:
- Android settings / Apps / Show system apps
- Choose Calendar storage (not the Calendar app)
- Storage / Clear data (locally deletes all unsynced events, too – won’t delete anything from the server)
- Force-sync in DAVdroid
Does that help?
@rfc2822 See above. That was already suggested to me, and it didn’t help. Wiping the entire cache partition (as suggested by Huawei) also didn’t change anything.
Were you using an emulator running a Huawei EMUI?
@6042114fa0 I see, sorry, I haven’t read the whole thread again. There is no Huawei image in the Android SDK.
Unfortunately I don’t have any further hints. I guess it must be something specific to your device. If there’s something certain I can do for you, just let me know.
Finally figured out the reason for this. In Zimbra, there is a recurrence rule “Every weekday”. This causes the error. Setting the event to the (equivalent) rule “every week” (with only “Monday”, “Tuesday”, “Wednesday”, “Thursday” and “Friday” enabled) does not cause the error.
It apparently doesn’t like this bit:
…whereas this one is accepted:
Can we do anything about this?
FREQ=DAILYhas worked in my local test, so it must be specific to your Android version/firmware. Can you update to a newer Android version?
I am of course using the newest Android available for my Huawei P20 Pro.
It must be due to
DAILYbeing combined with a set of days.
@6042114fa0 Do you think there is anything I can do in this case?
Not sure whether you’re in regular touch with the support teams of device manufacturers? Probably more than myself.
@6042114fa0 We file some reports from time to time (if we can find a way to do so), but usually we don’t get an answer nor are the requests taken seriously. Seems that as long as Google calendar sync works, there’s nothing to do
I can try with an older image, 4.4 from the emulator and have a look there. Maybe it was a vendor-independent Android problem and has already be fixed (but maybe not in your firmware yet).
I have tried again and couldn’t reproduce the problem with plain Android (Android image from SDK), neither with 4.4 nor with 9.0.
However, I have seen that we have received one or two reports about this problem earlier. Seems that some special devices don’t like
Like here in the forum? Didn’t find any.
@6042114fa0 I have found emails where this was reported … but very rarely.