Could not fetch collective details

[michiey]

Hi,

Describe the bug
When a Collective is shared with a group, every group member sees the error message "Could not fetch collective details" whenever they open the Collective, even though the Collective loads correctly and editing works as expected. The issue only affects users who have access through a group. It does not occur for the Collective owner, or when the same user is added directly to the Collective instead of through a group.
I tested this on two different Nextcloud AIO servers with the same result. Changing the group's role (Administrator or Moderator) does not affect the behavior.

There are no relevant log entries on the server and no hints in the browser console.

To Reproduce
Steps to reproduce the behavior:

1. Create a group and add a user to it
2. Create a Collective
3. Share the Collective with the group
4. Open the Collective as a user who is a member of that group (but not the owner)
5. The message "Could not fetch collective details" is displayed

Expected behavior
The Collective should open without displaying the error message, since everything appears to function normally.

Server details:

• Collectives app version: 4.4.2
• Nextcloud version: AIO Nextcloud Hub 26 Winter (33.0.6)

Client details:

• OS: Fedora KDE and Android
• Browser: Firefox

Best regards,
Mike

[max-nextcloud]

Hey @michiey

I tried to reproduce this locally but failed on the latest development version. So we'll need some help in tracking this down:

• Could you check the network tab of the browsers web developer tools for failed requests?
• Could you check the server logs for errors at the time in question?

[michiey]

Hi @max-nextcloud

After investigating the issue further, it turns out that this is not a Collectives problem after all, but rather a permissions issue related to Circles and our setup.

The browser developer tools show a 403 response for the following request:
GET https://nextcloud.[mydomain].de/ocs/v2.php/apps/circles/circles/dZtJzlxJPY6WwQjjZmEVgjGQQr1GPtw/members?fullDetails=true

I now noticed that the Collective only fails to display the members, which explains the error message.

For context: The users are not direct members of the Circle. Instead, they are members of a group, and only that group is a member of the Circle. If I add the users directly to the Circle, everything works as expected.

This makes me wonder if something has changed in the Circles app, as we did not experience this behaviour in the past. When a user opens the Circle in the Contacts app, they receive the message "There was an error fetching the member list", and the member list only shows "You currently have no access to the member list".

Our intention was to manage access to the content through group membership, without having to manage the users individually in Teams/Circles as well. Based on this behaviour, it seems that this is not possible in the way we expected.

Should I open a separate issue in the Circles app repository?

Thanks for your response.

Best regards,
Mike

[max-nextcloud]

@michiey Sounds like a bug in circles, yes.

Should I open a separate issue in the Circles app repository?

That would be great. Please mention this issue so the two are linked.

[michiey]

Thanks,

related issue in the Circles app: 2642