EOS_EComparisonOp::EOS_CO_ONEOF not supported for EOS_SessionSearch_SetParameter

The documentation claims EOS_SessionSearch_SetParameter function call supports EOS_CO_ONEOF for the comparison value (see doc links below)

https://dev.epicgames.com/docs/api-ref/functions/eos-session-search-set-parameter

https://dev.epicgames.com/docs/api-ref/enums/eos-e-comparison-op?lang=en-US

However, when I attempt to use this as part of the EOSGS OnlineServices interfaces I get these warnings / errors:

LogEOSSDK: Warning: LogEOSSessions: Container operation not supported yet.

LogOnlineServices: Warning: [FSessionsEOSGS::SetSessionSearchParameters] EOS_SessionSearch_SetParameter failed with result [EOS_NotImplemented]

Is this comparison operator actually not implemented or am I doing something wrong?

We’re trying to establish a build context for cross platform that filters to match one of any of X strings.

So we have something like the string being a semi-colon delimited list:

BuildContext=“MyBuildID;Filter2;Filter3”

This is using an unmodified version of the FSessionsEOSGS::SetSessionSearchParameters from 5.6.4 release. I am attempting to use this with the EOS libraries on GDK and Win64, same issue.

If this is not implemented feature yet, what is the preferred method here? Our goal is to allow consoles to have some developer support so that we don’t cross-talk with sessions in steam that publish a specific BuildContext, but in other cases allow it (such as on the default branch on steam), thats why the ANY OF filter would be useful for us. Currently our workaround is going to be to do multiple session searches to alleviate this lack of implementation, but I’m partially hoping something is just wrong with what I’m doing.

Thank you!

Hey,

This looks like a potential bug, though I’m not sure if it’s in the SDK, or if the parameter is incorrectly documented and the issue is in the UE plugin. In any case, you can workaround by updating the OSSv2 to EOS SDK mapping

case ESchemaAttributeComparisonOp::In: return EOS_EComparisonOp::EOS_CO_ANYOF;

Thanks,

Seb

Okay, so you’re saying instead of using EOS_CO_ONEOF, use EOS_CO_ANYOF?

Yes, that’s correct.

The header doc in the SDK is wrong. We’re updating it for the next release. It will now read:

	/** This one value is a part of a collection. Not usable in application search queries. */
	EOS_CO_ONEOF = 9,

EOS_CO_ONEOF is only used internally in the SDK for a specific use case.

We’ve also submitted a code review for the OSSv2 plugin with the change in my previous reply.

Thanks,

Seb

Thanks, will give it a go and report back!