Skip to content

[Bug]: Importing an event is not possible if an event with the same UID exists in the trash #53262

Open
Bug
Open
[Bug]: Importing an event is not possible if an event with the same UID exists in the trash#53262
Bug
Labels
1. to developAccepted and waiting to be taken care of32-feedbackbugfeature: caldavRelated to CalDAV internals

Description

@kesselb
kesselb
opened on Jun 2, 2025

Bug description

Importing an .ics file is not possible if an event with the same UID exists in the calendar trash bin. This issue is a regression from pull request #51924, caused by the unique index across calendarid, calendartype, and uid.

Steps to reproduce

  1. Import a calendar event into the calendar.
  2. Delete the event.
  3. Verify that the event is in the trash bin.
  4. Attempt to import the same .ics file again.
  5. 💥

Expected behavior

No error ;)

Nextcloud Server version

master

Additional info

Possible fixes:

  1. Extend the index to include the deleted_at column.
  2. Revert the calendar export changes and replace them with a simpler version for now (see discussion feat: Calendar Import #51925 (comment)).

Activity

  1. kesselb
    added
    bug
    0. Needs triagePending check for reproducibility or if it fits our roadmap
    on Jun 2, 2025
  2. github-project-automation
    added this to 🧑‍🤝‍🧑 Community triageon Jun 2, 2025
  3. github-project-automation
    moved this to To triage in 🧑‍🤝‍🧑 Community triageon Jun 2, 2025
  4. kesselb
    added
    1. to developAccepted and waiting to be taken care of
    feature: caldavRelated to CalDAV internals
    and removed
    0. Needs triagePending check for reproducibility or if it fits our roadmap
    on Jun 2, 2025

  5. kesselb commented on Jun 2, 2025

    @kesselb
    kesselb
    on Jun 2, 2025
    ContributorAuthor

    cc @ChristophWurst @SebastianKrupinski @st3iny

  6. szaimen
    added
    32-feedback
    on Jun 2, 2025

  7. ChristophWurst commented on Jun 2, 2025

    @ChristophWurst
    ChristophWurst
    on Jun 2, 2025
    Member

    Bummer. What was the reason against going by URI as suggested initially at #51924 (review) @SebastianKrupinski? edit: it's right there

    No we can't use the URI, the URI is never exported, it is a internal reference so there is no way for any automation to know about it.

  8. SebastianKrupinski commented on Jun 2, 2025

    @SebastianKrupinski
    SebastianKrupinski
    on Jun 2, 2025
    Contributor

    We just need to modify the index to add the deleted_at as the third reference.

  9. szaimen
    moved this from To triage to Confirmed in 🧑‍🤝‍🧑 Community triageon Jul 8, 2025
  10. susnux
    added the
    Bug
    issue type on Jul 14, 2025
  11. kesselb
    added this to 💌 📅 👥 Groupware teamon Aug 21, 2025
  12. kesselb
    moved this to 🧭 Planning evaluation in 💌 📅 👥 Groupware teamon Aug 21, 2025
  13. ChristophWurst
    removed this from 💌 📅 👥 Groupware teamon Jun 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    1. to developAccepted and waiting to be taken care of32-feedbackbugfeature: caldavRelated to CalDAV internals

    Type

    Bug

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions