@lje If you need to parse vCards, I strongly recommend to use a specialized library so that you don’t have to deal with those details (and there are many of them). DAVdroid uses the great library ez-vcard for that purpose.
Keep record of ignored vcards/iCals
When a vCard/iCal could not be processed, no database entry is created, so this entity will be downloaded at every synchronization.
Keeping record of unparseable/unuseable (for instance, unsupported VTODO entries etc.) would avoid downloading unuseable data again and again.
we should store it internally in davdroid, no? Do you need contentprovider for that?
I don’t know if this is required anymore because
- there shouldn’t be unparseable records in normal operation,
- as soon as other components like VTODO are supported, this will be obsolete.
Closing for now.
I’m not sure how DavDroid currently handles unparseable items, but it should somehow notify the user that something went wrong while parsing such items – otherwise the user could miss events, deadlines etc.