Errors after importing to Unity 2018.4.20f1 UWP project

[jasonhbartlett]

• Unity version: 2018.4.20f1

  • Scripting Runtime Version: .NET 4.x Equivalent

  • Scripting Backend: IL2CPP (Also tried .NET)

  • Api Compatibility Level: .NET 4.x

• Mapbox SDK version: v2.1.1 (latest from github)

• The platform you're building to: UWP

• A description of what you're trying to do: Add Mapbox to a HoloLens 2 app

• Steps to recreate the bug if appropriate:

  1. Clone the repo
  2. Open in Unity, select Mapbox folder, export (unchecked include dependency's)
  3. Open my Unity project with versions specified above
  4. Import the Mapbox folder

• Links to your logs are also helpful:

  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(14,4): error CS0246: The type or namespace name 'UnityTest' could not be found (are you missing a using directive or an assembly reference?)
  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(14,4): error CS0246: The type or namespace name 'UnityTestAttribute' could not be found (are you missing a using directive or an assembly reference?)
  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(9,3): error CS0246: The type or namespace name 'TestFixture' could not be found (are you missing a using directive or an assembly reference?)
  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(9,3): error CS0246: The type or namespace name 'TestFixture' could not be found (are you missing a using directive or an assembly reference?)
  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(7,20): error CS0234: The type or namespace name 'TestTools' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)
  Assets\Mapbox\Unity\Tests\MapboxUnitTests_AbstractMapTests.cs(5,8): error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)

[brnkhy]

@jasonhbartlett ah so it couldn't find the dll when build target is set to Hololens? I remember having similar issues with other dlls before but that one is rather new so we probably looked over it. Thanks Jason!

[brnkhy]

@jasonhbartlett are you downloading the package or pulling latest from dev branch? I also think you can just delete test folders as a temporary solution. Looks like NUnit doesn't work for some reason. Maybe it doesn't work with your build target, similar to that other issue?

[jasonhbartlett]

@brnkhy Yeah I'm cloning this repo directly. I just ran through the steps again just to clarify and remove any other unknowns. And I may have discovered something that perhaps may help you figure it out what's going on.

1. Clone the repo and open in Unity 2017.4.35f1.
2. Export all folders to a package
3. Create a new project in Unity 2018.4.20f1
4. Import the package with all folders.

With that I'm getting those 6 errors. Also, it's NOT popping up the Mabox Setup window (for putting in the access token.

But what I just found is that by going to Build Settings and changing the Architecture from x86_64 to x86 - the errors go away! And the Mapbox Setup window just popped up!

Now testing switching back to x86_64 ..... and... nope... errors NOT returning. I guess that fixed it? I guess it just needed to be temporarily targeting x86 architecture?

Weird. Any idea why that might be the case?

[jasonhbartlett]

Oh, hold up. I do get those errors again if my platform target is UWP. But they only show up when I go and toggle the scripting backend from IL2CPP to .NET or from .NET to IL2CPP. And now they are not going away.

Okay, if I delete the Tests folder under Mapbox/Unity then I don't have those errors any more.

I tried building after that and I did have one build error (other than the one I can fix related to the MapboxAccounts dll ) from my other Issue #1612

Assets\UnityARKitPlugin\ARKitRemote\ObjectSerializationExtension.cs(3,47): error CS0234: The type or namespace name 'Binary' does not exist in the namespace 'System.Runtime.Serialization.Formatters' (are you missing an assembly reference?)

But since I'm not using UnityARKitPlugin I can delete that and its not problem.

So I guess I have temporary fixes for all my issues in Unity 2018.4 UWP

1. Delete the Tests folder
2. Add a check for WSAPlayer on the MapboxAccountsUnity .dll

Question: Will this SDK be allowing for switching to the IL2CPP backend at some point as .NET backend is going to be depreciated?

If you have all your notes on this and want to close this ticket, that's good with me. Thanks the work on this.

[brnkhy]

@jasonhbartlett I'm kind of confused, do you think it's IL2CPP setting or UWP build causing this? Because (I think) I remember working with IL2CPP without issues. I was under the impression that it's the UWP causing the issue.