Thanks. Works without problems here… which Android version do you have? May non-compatible TLS ciphers?
IMPP with : in value can't be uploaded
Steps to Reproduce
- Edit a contact via default address contacts app
- Add a “custom” messenger type and give the type a name, such as “Ring”
- Enter an ID such as “ring:0123456789abcdef”
The contact should sync as usual.
Sync fails on PUT request (synchronisation phase 4) for the edited contact.
CyanogenMod 13.0-nightly (not up-to-date though)
Hello, please provide debug info and verbose logs. I guess there is some problem in the URI encoding of the
I have just followed your steps, and this is the VCard generated by DAVdroid:
BEGIN:VCARD VERSION:4.0 PRODID:+//IDN bitfire.at//DAVdroid/1.2 vcard4android ez-vcard/0.9.10 UID:86deb5fe-811b-48ea-96b2-40bd7339a7e5 […] IMPP:Ring:ring:012345 REV:20160705T220750Z END:VCARD
IMPPvalue looks as expected, and there was no upload error.
By the way, why the “ring:” prefix in the value, if you have already chosen Ring as custom type?
I guess your server doesn’t unterstand this
IMPPvalue and thus throws an error.
As said above, debug info, verbose logs and detailed steps to reproduce (including server and client versions, setup etc.) would be required to trace this problem.
Thanks for looking into this.
I didn’t provide any logs because I’m unable to anonymise them without potentially destroying useful information. I’ll try reproducing the issue with a new contact and post a log for that.
Unfortunately I can’t say much about the server. I am using the address book provided by Posteo but I don’t know what they use internally.
And as to why I’m still adding “ring:” to the IMPP string: It’s actually automatically added by the Ring app. I guess that’s simply the format of their IDs.
I was pretty sure the issue was due to the new value of the IMPP field since sync failed for the exact two contacts that I had linked with their Ring IDs. It must have been something else though, since I have also been unable to reproduce the problem with a fresh contact. I have worked around the issue by deleting and re-creating both problematic contacts.
I guess this thread can be closed now. Thanks for your time.