For those using cloud-connected calendars on multiple devices, it’s important to remember that the connecting middleware such as DAVx5 also needs to run in the background.
That was also already the case on my phone. But I decided to toggle the permission off then on, without actually launching the app.
A few minutes later the calendar on device B finally received an entry that had been registered in the cloud data hours before and created on device A hours earlier still.
Any developer knows that unfortunately parameter values shown in the UI don’t always reflect the values implemented by software. It’s sometimes useful to rewrite key parameters in the context of a software malfunction.
When you tap on “Allow background usage” (not the slider beside it) you should reach another menu where you can select “optimized” or “unlimited”. Maybe it’s worth a test to select “unlimited” there…
I think I’ve already tested that but I’ve reinstalled aCalendar because I missed many appointments.
I’ve now setted the option and will try to see if this changes something (tbh it seams that the reinstall made things better but not solved the problem completely).
Will report here, thanks for all your ideas and help