meta.xr.sdk.core conflict

[Kushulain]

While updating to a recent version of meta's plugin, it triggered this error when compiling:

Library\PackageCache\com.meta.xr.sdk.core@74.0.2\Scripts\Util\Async\OVRTask.cs(905,17): error CS0433: The type 'ManualResetValueTaskSourceCore<TResult>' exists in both 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' and 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'

Disabling Microsoft.Bcl.AsyncInterfaces from build (unchecking every platform in Unity inspector) will make the game to compile in Editor, but build fails with this error:

Building Library\Bee\artifacts\Android\ManagedStripped failed with output:
D:\Unity\2022.3.61f1\Editor\Data\il2cpp\build\deploy\UnityLinker.exe @Library\Bee\artifacts\rsp\805996784963018426.rsp
Fatal error in Unity CIL Linker
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'

Probably because XsollaBrowserLibrary.dll has a strong dependency on Microsoft.Bcl.AsyncInterfaces.

Sample of code from OVRTask.cs:

using System.Threading.Tasks;
using System.Threading.Tasks.Sources;

[...]

private class TaskSource : IValueTaskSource<TResult>, OVRObjectPool.IPoolObject
{
    private ManualResetValueTaskSourceCore<TResult> _manualSource;  **<-- happens HERE**
    public ValueTask<TResult> Task { get; private set; }
    [...]
}

We potentially have ways out of this, because I don't think we use the in game browser, and we don't ship our game with VR enabled in our Xsolla product. But it still require us to make custom changes to the plugin, which we will have to re-apply at each update.
(if I'm not mistaken about all this)

thank you!

[Kushulain]

This should reproduce with v2.2.0 or newer. with the plugin install via unitypackage. And meta.xr.sdk.core install via package manager. Unity 2022.3.61