Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homesets are not "personal" when they are detected two times (1x personal, 1x non-personal) #847

Open
2 tasks done
rfc2822 opened this issue Jun 11, 2024 · 0 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@rfc2822
Copy link
Member

rfc2822 commented Jun 11, 2024

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

No response

Steps to reproduce

Create a DAVx5 account with a service that lists home-sets under multiple principals (e.g. mailbox.org). URL hierarchy:

  • the user principal is something like /users/3, which contains both
    • a /carddav / /caldav homeset
    • group memberships in /principals/groups/0 (display name "Addressbooks")
    • and /principals/groups/1(display name "Standardgrouppe").

Actual result

DAVx5 queries the group principals, which again contain the /carddav / /caldav homeset. So the homeset is first detected as personal homeset (directly within the user principal), but then overwritten as non-personal homeset (from the group principals).

Expected result

If a home-set is detected as both personal and non-personal, it should be treated as personal.

Further info

No response

@rfc2822 rfc2822 added the bug Something isn't working label Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant