MLPlanesQueryFlags does not exists [..] - after upgrading from 1.9.0 to 1.10.0

Unity Development
1

I've upgraded ML SDK from 1.9.0 to 1.10.0 within Unity Package Manager and I kept getting the following:

image
image2744×388 70.2 KB

Library/PackageCache/com.magicleap.unitysdk@1.10.0/Runtime/Subsystems/Planes/Extensions/MLPlanesQuery.cs(23,62): error CS0426: The type name 'MLPlanesQueryFlags' does not exist in the type 'PlanesSubsystem.Extensions'

I'm also on ARFoundation version 5.0.7.

Any clues what I could be missing here?

Thanks,

Unity Editor version: 2022.3.0
ML2 OS version: 1.4.0-dev1
MLSDK version: 1.4.0-dev1
Host OS: MacOS

2

Hi @rafal.legiedz,

Thank you for bringing this issue to our attention. Is this a blocker for you? Is this issue appearing in the MLSDK Examples project?

Best,

El

3

I don't think it's a blocker as I don't target anything specifically from 1.10.0, thus I'm fine with 1.9.0 atm.

I haven't tested that with MLSDK Examples.

4

I have the same issue. Was it ever actually solved or do we just need to stay downgraded until a future version?

5

I had the same issue when upgrading from 1.10.0 to 1.11.0 (which just came out). I then closed Unity and deleted the auto-generated folders, Library, obj, temp, in the project folder (they might not all exist in your case) - and when I restarted, and Unity had re-imported, it no longer had those errors. Note that you will have to switch build platform to Android again, but this can also be done when opening the project from the Unity Hub.
At least I think that it was the deletion/regeneration of those auto-generated folders that did the trick, but it might be that I did something else as well that I don't remember...

6

@rafal.legiedz Does upgrading to the latest version of the Unity SDK fix this issue?

Thank you @JakobAnarkyLabs

7

It seems that I had the same issue when upgrading from 1.10.0 to 1.11.0 as @rafal.legiedz had when upgrading from 1.9.0 to 1.10.0, so maybe it is just something that can happen when upgrading from one version to another. Anyway, for me the error disappeared when I deleted those auto-generated folders and let Unity re-create them.

1 Like