VALARM ACTION:EMAIL is converted to ACTION:DISPLAY when syncing (Android 16, Nextcloud 32.0.5, DAVx5 4.5.9-ose)

[topcaser]

Problem scope

• I'm sure that this is a DAVx⁵ problem.

App version

• I'm using the latest available DAVx⁵ version.

Android version and device/firmware type

Android 16 (Pixel 8 pro, GrapheneOS)

Steps to reproduce

EnvironmentDAVx⁵: 4.5.9-ose (GitHub build)
Android: 16
Server: Nextcloud 32.0.5
Calendar app creating event: Fossify Calendar (set reminder type “Email”)

Expected: Server should receive VALARM with ACTION:EMAIL (or at least preserve it on upload)

Actual: Server receives ACTION:DISPLAY (Nextcloud UI shows “Benachrichtigung”)

Reproduction steps
Create event in Fossify Calendar with email reminder (e.g. 1 day before).
Export event locally -> ICS shows:BEGIN:VALARM … ACTION:EMAIL … END:VALARM
Trigger DAVx⁵ sync.
Export the same event from Nextcloud Web -> ICS now shows:BEGIN:VALARM … ACTION:DISPLAY … END:VALARM

Question
Is converting ACTION:EMAIL → ACTION:DISPLAY intended because of Android provider limitations, or is this a bug/regression?Is there a setting/flag to preserve ACTION:EMAIL when uploading to server?

Actual result

No response

Expected result

No response

Further info

No response

[rfc2822]

Is your account name a valid email address? Otherwise, how should DAVx5 know which email address it should use? The mapping code can be found here:

https://github.com/bitfireAT/synctools/blob/446a74dcc55171913595499fcd297eb28c45131e/lib/src/main/kotlin/at/bitfire/synctools/mapping/calendar/handler/RemindersHandler.kt#L37-L68

[topcaser]

Wow, that is unbelievable, how simple can it be. I just needed to rename the account name to my email address. Everything is working fine now. And I struggled a long time with that inconvenience. Thank you so much. Bernd