@rfc2822 https://gitlab.com/bitfireAT/davx5-ose/-/commit/e157322a1fcbd23c26263f31c2adb1218ec4843a

Done, thanks.

Thanks. If you find any hint in the standard that EXDATE should always have the same time zone as DTSTART (what if DTEND has a different one?), please let me now 🙂

Yes, it does - you’re awesome, thank you very much! 🙂

Available in 2.5.5, which has already been released and should appear in F-Droid as soon as they have compiled it.

Hm, it’s reliably reproducible here using the Android emulator and testing different Android versions (8.1 and 9.0).

I’ve attached a logcat.txt from a failing test run. logcat.txt
Maybe that helps in finding the cause of the failure.

@rfc2822 just to give you a bit more of context, we have replaced the old network library in the ownCloud Android app and started to use OkHttp along with dav4android to perform the WebDAV requests. Besides, we released a new app version recently (2.8) and we would like to release 2.9 with the new library using OkHttp and dav4android soon.

Thanks!

At the moment, we’re not targeting plain Java for cert4android, but it would be a good idea if other people are actually using it, too. For which projects are you using it?

We are using it for Nextcloud Notes ( https://github.com/stefan-niedermann/nextcloud-notes/ ) and I plan to integrate it in another Nextcloud-related app.

Until then, does CustomCertManager.Companion.resetCertificates(Context) work?

Yes, that works! Thanks, that’s sufficient for now. But it would be nice, if you could keep in mind that also (plain) Java projects may use cert4android.

Thanks!

Great! 🙂

I think that you can switch back to your old notation using 26.+ (if you really want), since you’ve added the new Google maven repository.

However, you have the same “problem” with the build tools. And for both cases, Android Studio should notify you in case of updates. Unfortunately, there was no notification for the new maven repository.

I don’t have any time at the moment but I will update this topic once I do