With Unity 2018.4 LTS, you might see compiler errors like below when using Vuforia:

Assets\Vuforia\Scripts\Internal\RuntimeOpenSourceInitializer.cs(61,63): error CS0234: The type or namespace name 'ScriptableRenderContext' does not exist in the namespace 'UnityEngine.Rendering' (are you missing an assembly reference?)

This can be easily resolved by opening that script, and change all occurrences of

#if UNITY_2018_3

to:

#if UNITY_2018

We are aware of the following known issues with Unity 2019.1. They are not seen with Unity 2018.3, so for now we recommend to stick to that version.

Update: this has been fixed in Unity 2019.1.4f1

We are currently looking into a known issue where errors like the following are displayed after importing a Vuforia sample from the Asset Store into Unity 2019.1:

Library/PackageCache/com.unity.package-manager-ui@2.0.3/Editor/Sources/UI/PackageDetails.cs(5,32): error CS0234: The type or namespace name 'UIElements' does not exist in the namespace 'UnityEngine.Experimental' (are you missing an assembly reference?)

Hello,

We are currently aware of two known issues with Cloud Build and are working closely with Unity to resolve them:

Hello,

A regression was introduced with Vuforia SDK 7.5.26 in Unity where using the .NET scripting backend will throw an exception when running a Universal Windows Platform build. This also includes HoloLens apps.

Please use the IL2CPP scripting backend instead, where this issue is not seen. We plan to fix this issue in an upcoming release.

Summary:

Hello all,

A crash is seen on iOS when using Vuforia 7.0 in the Unity 2017.4 LTS version (2017.4.5 and later) when using Metal graphics API and Autorotation. There is a work around available. Disabling the "Multithreaded Rendering" option in Player Settings will prevent this crash from occurring.

This issue is not present in more recent versions of Unity and Vuforia. Unity 2018.1+ and Vuforia 7.1+ do not encounter this issue and can be used without the workaround.

Hello,

Recently, Vuforia released 7.2 SDK with updated samples to the Unity Asset Store. These samples are not compatible with the 7.1 SDK, which is already packaged with most (if not all) of the current versions of the 2018.1 and 2018.2 Unity Editor.

The most common Vuforia error message observed is the following: "The type or namespace name `FusionProviderType' could not be found. Are you missing an assembly reference?"

Hello all,

There is an issue with Vuforia 7.2.20 that will prevent you from uploading your iOS app to TestFlight. The cause of the issue is that the “Bundle Version” field of the Info.plist in the Vuforia.framework is blank. This issue can be worked around by opening the Info.plist file and adding a number value, such as “1,” to this field.

Hello All,

The steps for patching the Vuforia version in Unity 2018.1 when it is installed via the Unity Hub is a bit more involved when on a Mac. The follow instructions are meant to guide you through this upgrade process.

Note: These steps are for Mac. Updating on Windows can be done by running the Vuforia upgrade package and selecting the version of Unity within the Hub directory which can be found in C:/Program Files/Unity/Hub/Editor/<your version>

An archive of sticky topics as posted by Vuforia moderators.

Note that some links and topics may have been moved, or are no longer available. If this is the case, we apologize for the inconvenience and suggest that you search the forums to find an answer to your questions.

Thanks,

Vuforia Support