Error on Building to WebGL - Colliding Plugins?
Hello, Meta forums! My team is dealing with an issue regarding building to webGL with a Unity project that includes the Oculus Meta All-In-One package. Specifically, whenever we try to build to WebGL, we receive this error: Plugin 'InteractionSdk.dll' is used from several locations: Packages/com.meta.xr.sdk.interaction/Runtime/Plugins/Win64/InteractionSdk.dll would be copied to <PluginPath>/InteractionSdk.dll Packages/com.meta.xr.sdk.interaction/Runtime/Plugins/Win32/InteractionSdk.dll would be copied to <PluginPath>/InteractionSdk.dll Please fix plugin settings and try again. UnityEditor.Modules.DefaultPluginImporterExtension:CheckFileCollisions (string,string[]) UnityEditorInternal.PluginsHelper:CheckFileCollisions (UnityEditor.BuildTarget,string[]) UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) Plugins colliding with each other. We're not sure why this duplication is happening. We found that removing the dll file from the Win32 folder prevents this error, but we consider this a band-aid solution that we'd have to do each build. Since the dlls are managed by the UPM, we're unable to modify the import settings to exclude them for the WebGL platform ourselves. Are there any configuration settings or other solutions we could use to solve this? Important note: we aren't trying to implement VR in WebGL. However, our project does have a WebGL build and would like to maintain this build on the same branch, if possible.1.9KViews1like3Comments
Oculus Integration as custom package dependency
Hi, is there a way to declare Oculus Integration as a dependency or have it linked somehow to a custom UPM package? I am trying to build a custom core package with Quest hand-tracking setup and a couple of features to be able to reuse them in multiple projects. Since Oculus Integration is available as an asset instead of a UPM package, I cannot reference the dependency in the manifest. Attempt to move the whole Oculus Integration folder from project Assets to my custom package failed. According to this answer from Unity, Unity Asset store packages are a legacy way to share content and new assets should be switching to UPM. Any chances Oculus is planning to switch to UPM soon? I would appreciate any suggestions!1.9KViews2likes4Comments