invite.exists returns more results than invite.pending + invite.accepted + invite.rejected

[Jan-Stepien]

Which packages are you using?

stream_chat

On what platforms did you experience the issue?

iOS, Android

What version are you using?

stream_chat: ^6.6.0

What happened?

when calling await _chatClient.queryChannelsOnline(

with

filter: stream.Filter.exists('invite'),

and

filter:  stream.Filter.or(
    [
        stream.Filter.equal('invite', 'pending'),
        stream.Filter.equal('invite', 'accepted'),
        stream.Filter.equal('invite', 'rejected'),
    ],
)

returns different results - meaning there is more values to query for in terms of invite parameter ( not shown by the documentation)

Steps to reproduce

Call await _chatClient.queryChannelsOnline(filter: stream.Filter.exists('invite'),)

and

await _chatClient.queryChannelsOnline(
    filter:  stream.Filter.or(
        [
             stream.Filter.equal('invite', 'pending'),
             stream.Filter.equal('invite', 'accepted'),
             stream.Filter.equal('invite', 'rejected'),
        ],
    ),
);

2. compare result sets

filter: stream.Filter.exists('invite') returns more results than

filter:  stream.Filter.or(
    [
        stream.Filter.equal('invite', 'pending'),
        stream.Filter.equal('invite', 'accepted'),
        stream.Filter.equal('invite', 'rejected'),
    ],
)

Which leads me into thinking that there are more statuses that are not exposed.

Supporting info to reproduce

No response

Relevant log output

No response

Flutter analyze output

No response

Flutter doctor output

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[Jan-Stepien]

Whats the status on this one? Its pending invite implementation blocker issue

[github-actions[bot]]

This issue is stale because it has been open for 20 days with no activity.

[esarbanis]

Hey @Jan-Stepien , looking into this, I am sorry for the delay.

[Jan-Stepien]

No worry @esarbanis is there any way i can help you or is it clear?

[deven98]

Hey @Jan-Stepien 👋

After checking with the backend team, the invite.exists filter is not the appropriate filter to use for checking for all invite states. The second filter you used is the correct one in this scenario. Invites were not meant to be checked with the exists filter and the newer backend query parser throws an error when this is used.

Hope this helps - closing this for now. Thanks!