@devvv4ever Thanks for your follow up. I was syncing to the Synology Calendar “My Calendar”. To be sure I changed the name to something very distinctive and posted on my phone making sure I was posting to that calendar. And it worked! So guess it was user error on my part. Thanks again for your help.

@rfc2822 I think I’ve figured out the reason for the error message.
When I previously tried to enter the ip-adress, I asked the app to prepend https://, which is probably the reason why it didn’t allow for “:5001” to work. My best guess is that the app does the error check without virtually prepending https.
Tested it while manually adding https and port, and now it is working flawlessly.

Thank you very much.

@devvv4ever

Your support is as excellent as Your app - thank You so much…
Best, Steffen

@rfc2822 said in [Solved] Nextcloud Contacts Birthdays calendar : http 404 error:

But then how to distinguish the errors? Every notification should provide verbose information, including debug info, about the problem so that it can be traced.

That’s why there is an app’s status function, all this sent multiple times (esp in the case for different feeds to the SAME server) to a mobile phone’s notifications is over the top.

Yea but every time I click on a single notification and reload the fetch and it always works, it is too much to have multiple notifications, one will suffice in any case

Perfect, thank you! This clears everything up. (Sorry I missed that FAQ page – I looked through the titles but that one hadn’t jumped out at me at the time.)

Just sent the APK. Android 11 introduced new “awesome” features – wohohohoo – like this package visibility, but it seems due to a bug in Android 11 the visbility of our declared providers gets lost after a few days. Now we changed it to the package names instead of the providers we want to see - hopefully this fixes the problem…

I finally solved this last problem. I posted it on SE: https://android.stackexchange.com/questions/230983/the-phone-as-hotspot-doesnt-use-its-own-dns/231206#231206
It turns out this is expected behavior: the phone as a DNS client doesn’t use the DNS server it runs.

However I installed Virtual Hosts which allows to define custom hosts entries without rooting the phone. The app is really easy to switch on/off, so I’ll be able to use it only when I sync DAVx5 (which I do manually only) through the phone access point.

Happy syncing!

I can confirm that 3.3.5 from F-Droid no longer has this issue. Thanks for the quick turnaround!

@rfc2822 thanks so much!

@bigboypete The commit Don’t ask for active location services on Android <9 / location permissions on Android 8.0 was after 3.3.5 and will be contained in 3.3.6.

But as soon as you get Android 8.1 or newer, you’ll of course get the notifications again.

@j-ed Thanks - it wasn’t DavX5 I was screaming about but the logic of the Android Contacts set-up. I realise the droid contacts app is a consolidation of a whole lot of backends - so if you’re taking something out of one backend to put it in another backend, then it ends up going in and out the front end… (I’m not trying to be indecent, honest

Anyway, sorted. Thanks.

ah ok that makes it a lot easier. actually that’s the information i was looking for, but in the wrong place. everything is working fine now, thanks a lot for the help

@Thabor Thanks for the update! Probably there was some temporary problem.

So it’s solved for you? Fine, I’ll set the topic to resolved.

Maybe supporting local syncs without Internet will be possible with DAVx5 some day (I’d love to see that). But first there are many things to do

Hi again,

i have been trying that as well now - however i am still not sure about the exact details and order.

delete the address book on Synology,
( The CardDav Server is creating one Addressbook per user - i am admin and therefore i cannot just delete the addressbook in question)

create a new empty address book,
I assume that this should be done on the phone as the Synology would also not allow me to do that.
And when we speak about phone do you mean in the contacts app or the DAVx5 ( the last one i tried with below result)

Here is what i have been doing:

deleting the contacts from phone again deleting the contacts from CardDav Server Attempting to import the contacts.vcf from phone into DAVx5 Account (Phone) This did not work (no specific error - just cant be imported presented by Android) deleted the DAVx5 addressbook on the phone via DAVx5 App Attempting to create new Addressbook via DAVx5 in App - does not work with an error 403 Forbidden

Can you specify exactly where each action has to be performed ?

Thanks in Advance.

Ok never mind the above - the import that showed me not possible before worked now - the downloaded file was empty - i could retrieve it though. The issue was resolved exactly as you told me… I have to document that for myself in case that it will happen again.

Thanks a lot for the quick help and replies…
Really enjoying the app so far- keep up the good work.

Thanks a lot again

Thanks for the update!

@NisiMasa Great to hear! However its sad that you had to wipe the whole device to get it to a good condition again.

@loiselqw said in syncing with yandex carddav does not provide anniversary information:

Does it make sense if I sent you via private message a App Password so that you could reproduce both issues?

Yes, if it is account specific, please send the data using “chat” / private message or the contact form on https://www.davx5.com/contact

i get some similar error:

EXCEPTION: java.lang.OutOfMemoryError: Failed to allocate a 8227872 byte allocation with 2097152 free bytes and 5MB until OOM at...

so i think this means >8MB .vcf file-size ?!

Thanks @hokuspokus for the hint with the big profile photos.
(i only have 53 contacts in this addressbook…)

how i found the contacts with big pictures:
in thunderbird CardBook i export my address book as directory.
this generates one .vcffile per contact -
then i sorted this folder with my file-manager after the size…

sunny greetings
stefan

Should have been fixed and will be shipped with the next version. Thanks for reporting!