Actually I didn’t have a particular client in mind when implementing this feature, but wanted it to be vCard 4.0
compliant. I think RFC 6350 is pretty clear that for URI’s which are used for voice communication TEL properties should be preferred, and the SipAddress data kind in Android is only used for voice calls AFAIK. (The SipAddress data kind is displayed as “Internet Call” in the standard contacts app “People”.)
Please update support-libraries
We are using cert4android in our open source project and found out, that the version 26.0.1 of the support libraries has a bug (see https://github.com/stefan-niedermann/nextcloud-notes/issues/279 ). Since it’s only possible to use a single version of the support library in a project, I kindly ask you to update the support libraries in cert4android (26.0.2 fixes the problem, but 26.1.0 is released, too).
Is there a conflict when you use another version? I thought gradle can resolve this and use the “newest” conflict resolution strategy by default. Are you using the latest gradle version?
But I’ll update nevertheless
@rfc2822 Thanks for the hint! The automatic conflict resolution didn’t worked in our project, since there was a dependency in cert4android, that we hadn’t in our module. After adding
com.android.support:cardview-v7as dependency to our module, the conflict resolution works, now.
Hence, the problem is solved without updating
cert4android. Thank you very much!