Hello,
when synchronizing CardDAV address books, the CATEGORIES property is dropped.
I don't know which trashy lib the culprit is - unlikely it's ez-vcard this time, since exporting to vCard file keeps the CATEGORIES property intact.
So either DAVx5 or my provider mutilates the entry :-(
(how much I'd wish vCards would have gotten a checksum and no lib would be allowed to rewrite anything - it's ridiculous how the various libs handle each definition differenly, not only encoding wise... the real problem is, it's good habit to resize picture e.g. - horrible experience, each time I try to investigate why import/sharing never results in an identical copy :( )
So for me, currently contact scopes won't work by design as soon as (any? at lteast the one I tested) CardDAV address book enters the stage, since those apps which were restricted to read only entries with distinct labels won't see anything anymore - forcing me to disable contact scopes and give full permission.
If GrapheneOS developers could extend the scope to cover whole ("external") address books, this would circumvent the problem of the dropped CATEGORIES property.
Unfortunately I don't know much about how the address book store was designed for Android, I was astonisehd DAVx5 creates a separate address book apparently.
Can anybody else confirm the problem resp. maintain the contrary, that it's possible to keep labels/groups (defined in the CATEGORIES property) synchronizing CardDAV address books?
Thanks!