Thanks, that worked!
I exported all contacts into a vcf.
Deleted all contacts in the DAVx5 account and reimported from vcf.
Hopefully nothing got lost, can’t check everything in detail.
A bit of a long way round but at least it worked.
I see… What happens if you try curl -vX PROPFIND -u username:password http://oobee3hoosh2ocee.onion/remote.php/dav on the command line (you can use --preproxy to use a SOCKS proxy with curl)? Just to be sure that it’s really a proxy problem.
If you have a problem with DAVx⁵, please:
Try the latest DAVx⁵ version. Use the latest version of your server software, if applicable.
Read the Configuration, FAQ and manual pages carefully. The most common issues are explained there.
Try the forum search – most questions have already been answered.
Have a look at the debug info/error details/logs. You can often get an idea what’s the problem yourself.
Search the the Web for the problem, maybe ask friends who are willing to help.
Make sure that it’s not a server or networking problem. Search the FAQ/forums/bug tracker of your server software, too. Many supposed DAVx⁵ bugs are server or networking problems.
See also: FAQ: How to debug DAVx⁵-related problems
When posting, please provide as much information as you can:
Go to DAVx⁵ / Settings (left navigation drawer in the main screen) / Debug info. Send these information to yourself (using the “Share” action, for instance by email). Paste the info to fpaste.org or a similar service and provide a link. It contains the most important information about your device and configuration.
Describe exactly what you were doing (steps to reproduce), what you tried to achieve and what your problem is. Imagine someone else who wants to reproduce the problem to find a solution and provide all necessary information.
Give information about your environment: what is your server software (including version), what are your calendar URLs, do other clients work, etc.
If possible, try to explain what you already have tried to solve your problem.
If you get “No CalDAV/CardDAV service found” when you try to add an account:
Tap “View logs”. Send those logs to yourself (using the “Share” action, for instance by email).
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month).
If you get an error notification while synchronizing:
Tap the notification. A debug info activity will appear.
Send the debug info to yourself (using the “Share” action, for instance by email).
Paste the debug info (≠ logs) to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short debug output can be inserted in the text, but please quote with ``` (at the beginning and the end).
If additional logs are required to diagnose the problem, continue below.
Your problem doesn’t cause a notification or you need verbose logs?
DAVx⁵ / Settings (left navigation drawer in the main screen) / Enable “Verbose logging”. A permanent notification tells you that logging is now active.
Do whatever causes your problem (e.g. “Refresh calendars”, or initiate a sync).
Use the notification to share the log. You may have to expand the notification to see the “Share” action.
Send the logs to yourself (for instance by by email, or with Share with HTTP).
Remove private data from the logs, if applicable.
Paste the logs to fpaste.org or a similar service and provide a link (feel free to let it expire in a month). Short parts of the logs can be inserted in the text, but please quote with ``` (at the beginning and the end).
If your problem has been solved, it would be kind to let other people (who were willing to help you) know the actual solution.
notify on invalid tasks/vCard objects (events will follow)
add app setting for notification channels: Notification settings (only Android 8+)
use default time-zone to store floating DATE-TIMEs
exceptions of recurring events: use main event’s DTSTART time zone for RECURRENCE-ID
minor improvements and bug fixes
When you tap a notification about invalid iCalendar/vCard objects, you can see more information, including the URL of the invalid object. You can hide all “Sync warnings” in the app notification settings (Android 8+ only, because this depends on notification channels), but we recommend to care about these messages, because it means that some events/tasks could not be synchronized.
As far as I see, the problem is that Myself@example.org is not identified with yourself, isn’t it?
Yes it is, no doubts.
I was only justifying myself about how I’ve missed the casing issue at first sight
Maybe an advanced option like “normalize email addresses” could be added in account configuration?
Maybe together with a warning like “use only if you have issues with users adding mixed-case email addresses”
Is this acceptable or do you think it’s a “too geeky” workaround?
@heX16 That would certainly be possible, if there is no other solution (like fixing the problem where it comes from).
I’d really appriciate if you could contact the MyPhoneExplorers and tell me what they say? Android account names can easily contain Unicode characters, for instance if you use local language. What if you name an account “Mein schöner Account”? Or “мой аккаунт”? Such names should work with any app, and they’re not related to DAVx⁵.
The build was an official update from ~last summer. I didn’t update for a while, but I will do so this evening and hope that everything keeps working and the issue really was caused by a bug in the current build.