Thanks, it worked.

Hi, I don't think nextcloud is involved, since the sync settings are stored on the Android side. It must be some internal setting or problem of Android itself, because users of other device manufacturers also reported this over the last years, however it was a rather rare issue and we never could reproduce it except from the "maximum power saving issue" (Samsung devices only) which reproducibly sets sync to manual.

SOLVED!!! I learned how to back up the GMX-calendar in an ics-file. and the i dared to click "kalender neu erkennen" ("re-recognize calender"?) now everything is fine it would be great, if the manual would be easier for non-technicians like me. lg jochen

I have the same problem. This used to work fine at some point. I have a Nokia 7.1 with 8.1 Oreo. When I configure DAVdroid and then leave my phone alone for just a few minutes, synchronisation is disabled (both in the Android setttings and in DAVdroid). It seems that this problem is not exclusive to DAVdroid. I think I may have found the solution while typing this message: There is a background activity manager in Android, you need to explicitly allow background activity for DAVdroid there (Settings->Battery->Background activity manager - sorry if the names are not correct, this is a reverse translation from my German Android UI to English).

@rfc2822 Yeah, I thought I pasted a space after the URL. Maybe you can improve the UX here.

@rfc2822 I'm not able to reproduce the problem now. All attempts to create calendar entries of different types are working. If the error repeats I'll let you know. Thanks.

@erosion said in Fastmail/Thunderbird/Android Contacts Discrepancies after 'Copy Contacts' & Sync: As soon as there are 297 contacts in Fastmail, you don't need the app anymore. I don't understand what you're talking about here, as my goal is to keep all 3 contact repositories in sync: I meant that you don't need the "Copy Contacts" app anymore. Syncing between 3 places (one of them with DAVdroid) is a common use case. I'm syncing between Nextcloud / Evolution / DAVdroid myself. Everything works perfectly Happy that it now works for you. If there's still a specific problem, just let us know.

@devvv4ever For some reason after I updated Nextcloud, Davdroid was marking that it was syncing but Opentasks couldn't connect properly and wasn't registering any changes made on NC, and when adding a task with Opentasks, they didn't upload to NC either. What I did to start the troubleshot was to uninstall Opentasks and reinstall it. After that all worked fine:)

For reference and transparency: We have created this report on Apple Bug Reporter on 6 Sep 2016 here: https://bugreport.apple.com/web/?problemID=28172308 Summary: VCard 3 uses folding for long lines. OS X Server Contacts can't parse VCard 3 resources with folded PRODID lines. Steps to Reproduce: Upload a VCard 3 with folded PRODID line, like the following: BEGIN:VCARD VERSION:3.0 PRODID:+//IDN bitfire.at//DAVdroid/1.2.3-gplay vcard4android ez-vcard/0.9.1 0 UID:0ea1c5a9-2c93-443d-8672-0e871710203b@owncloud-service-host FN:John Doe N:Doe;John;;; … Expected Results: The VCard should be parsed correctly. Actual Results: VCard is not parsed. Console error messages: Ignored vCard at /remote.php/carddav/addressbooks/principalname/contacts/0ea1c5a9-2c93-443d-8672-0e871710203b%2540owncloud-service-host.vcf because there is no UID property: "BEGIN:VCARD VERSION:3.0 PRODID:+//IDN bitfire.at//DAVdroid/1.2.3-gplay vcard4android ez-vcard/0.9.1 0 UID:0ea1c5a9-2c93-443d-8672-0e871710203b@owncloud-service-host FN:John Doe N:Doe;John;;; TEL;TYPE=home;TYPE=pref:+1555123456789 EMAIL;TYPE=work;TYPE=pref:john.doe@example.com EMAIL;TYPE=home:from-mac@example.com EMAIL:from-davdroid@example.com REV:2016-08-14T13:18:42+00:00 END:VCARD" Version: OS X Server 5.1.5 Notes: Line folding is defined in RFC 2426 section 2.6, which refers to RFC 2425 section 5.81. Lines longer than 75 characters even SHOULD be folded. Configuration: This report was marked as a duplicate and the problem has apparently been fixed.

This is strange, because the synchronized birthday calendar is just a calendar like all others, and I don't think the Contacts app or what else should put birthdays into randomly selected DAVdroid calendars. Are you sure that you didn't try to change the birthday in the Calendar app? (But it shouldn't be possible anyway, because the calendar is falgged read-only.) I'll mark this as solved. If you find out something relevant or if there's anything I can do for you in this matter, just let me know here. PS: https://github.com/nextcloud/server/issues/11633 – 403 instead of 404 could help to understand the problem when someone encounters the error message

The issue has been fixed in Calendar v1.6.3

Damnit! Pebcak here, for some weird reason all calendars in "acalendar" were excluded from syncronisation. After I enabled them again, everything is fine again. Sorry for the mess, and many thanks for your support!

@saren-t said in "Couldn't parse iCalendar source" on validated iCal source: But also Lightning can read the same source without any problem. Yes, Lightning does not use the ical4j library, which is quite strict about this. I wonder what the original intention of the standard is, but I guess its purpose is that servers can detect the timestamp of entries without having to calculate time zones.

dont understand where the log went 0_1538479065223_debug.txt I reinstalled everything and now it works. Thanks for help

Thanks for the feedback @rfc2822! I tried over 4G (previously I was using WiFi) without success, but now I can see that the FastMail return 401 Unauthorized for my user. Alternatively, I tried connecting to caldav.fastmail.com as they described in on their side, but that failed with 401, too. 1_1538329346455_fm-debug4-4G-caldav.fastmail.com.txt 0_1538329346455_fm-debug3-4G-fastmail.com.txt This looks more like a FastMail issue, or? Ignore what I wrote. I was missing a letter from the FastMail generated app password. My bad! It works now with the https://caldav.fastmail.com/dav/ url. Thank you!

Hello again, I ereased the account, did the whole process again, now it works...

Ok, I understand. Is there any technical information I can pass over to them? I do not have any difficulties with "in deep" and "programmer-like" explanations as I a do backend development myself but never confronted with contact/account management under android. I will then pass that information over to blackberry to let this issue be fixed.

@herbert1 thanks for the update!

@alig2134 Thanks for the update!

@wwwampy Thanks for testing. We will release 2.0.4 soon!