Known issue when developing with Vuforia 7, Xcode 9.3 and iOS 11.3 beta (ARKit 1.5)

Using 2018.1.0b13 I cannot see the Vuforia Update link in the ARCamera, any way of getting this link so I can install manually?

 

Unity 2018.1.0f1 is now available via the Unity Hub. This version has access to Vuforia 7.1.34 which fixes the issue discussed in this thread.

 

Any update here? I downloaded 2018.1.0f1 and installed the latest version of Vuforia. I need to use the Core Samples back, but when downloading it from the asset store, it seems to revert back to a previous version (7.1.31) has anybody got Vuforia working for Unity 2018.1?

 

I would advise you either download the samples from the Vuforia website, or download the samples first then use the upgrade tool in the Vuforia configuration to update to latest.

It's all getting quite messy now, there needs to be a versioning system which can be selected either within the editor or via the website so we can download packages and samples for those versions. This was a major issue, and even though there was a workaround it's taken a long time for Vuforia to fix this. For a commercial product the support here needs to be better.

 

Is it possible to use 7.1.31 in Unity 2017.3.1? (patch 4 to be specific). If it is, how do we do it

 

Is Available as a beta release, right??

 

Agreed 100%. Thanks for the help.

 

The Unity Hub is saying it is a beta release, but it is using a commercial version numbering (0f1). I'll try to get more clarity on this, apologies for the confusion.

 

Hi,

I've had the same Problem. This internal update paket from Vuforia shown in unity mac to update to 7.1.34 seems to have an issue with the new unity hub. After deinstalling unity and unity hub complete and reinstalling only unity from the beta page, it went well and I got my upgrade to 7.1.34.

Greets,

Thies

 

Great, I'll give this a try. Thanks @gemelo

 

and surprise, vuf cam is working nice with 7.1.34 and unity 2018.1.0f1. Great. Thanks.

 

I feel like I can't get anything to work with Vuforia and Unity anymore. Using the 2017.4.1f1 version for Unity. Anyone else having these issues? It used to be so simple to create an image target and add the model to it, and then test it with the webcam. None of that seems to be working for me now. What happened? Are there extra steps I am missing that are new to this version?

Thanks

 

@gemelo works like a charm! Thanks for the help. I took it a step further and installed each component individually (Unity Editor 2018.1.0f, iOS Build Support, Vuforia Target Support) after I uninstalled my previous Unity version AND unity editor. Probably overkill but it worked. Thanks again man.

 

I just installed Unity 2018.1.0f1 and the link to "Vuforia Augmented Reality" in build settings under 'XR Augmented Reality" goes to an error page!! please help I have 3 hours to fix this issue. The link is: http://download.unity3d.com/downloa...-Vuforia-AR-Support-for-Editor-2018.1.0f1.pkg which goes to error page.

 

I had the same problem and resolved with the following steps:

• Open Unity Hub
• Go to the Installs Tab
• Under Unity 2018.1.0f1 click the 3 dots (right hand side of window)
• Click add component
• Choose Vuforia Augmented Reality Support

 

Still seeing this with Unity 2018.1.0f1. Any other settings we should be toggling? (E.g., we use delayed initialization in our apps--is this supported?). I have a client waiting for a build, this is directly affecting our business.

 

Ok, I take it back, 2018.1.0f1 still had 7.1.31. I installed it directly after having to move the 2018 Hub install into the normal Unity folder.

 

Thanks - I ended up downloading components separately from here: https://unity3d.com/unity/beta-download

The Unity Hub route sounds more user friendly though.

Unity 2018.1.0f1 + Vuforia 7.1.34 solved the problem for me.

 

I have a new problem following upgrading to Unity 2018.1.0f1 + Vuforia 7.1.34

I use the back facing camera for Augmented reality and switch to the front facing camera for taking selfies. The issue is now that for IPhone X IOS 11.3 devices, when i switch to the front facing camera it displays vertically inverted. For other IOS devices it displays fine. I am not applying any mirroring when I switch from back to front facing camera.

Code (CSharp):

1.  
2. CameraDevice.Instance.Stop();
3. CameraDevice.Instance.Deinit();
4. CameraDevice.Instance.Init(CameraDevice.CameraDirection.CAMERA_FRONT);
5. CameraDevice.Instance.Start();
6.  

Of note is that if the camera is switched to front facing, the view is inverted (upside down) as i described above. If you then exit the app, then open the app again, once Unity/Vuforia reinitialises again the front camera is NOT inverted. If the camera is then switched programatically to back facing then front facing once more, it is inverted again.

 

Today i tested Unity 2018.1 + Vuforia 7.1.34 and the issue is resolved. My AR app now works fine with the latest iOS devices.

 

Today I tried to install a vuforia 7.1.34 for Unity 2018
But this vuforia can only be placed on a unity 2017 and don't work with 2017. (Vuforia can't find exe Unity 2018)
If I use Hub, he install me only vuforia 7.1.31
Please, help me.

 

Can you be more specific... what has to be moved where? Unity folder in /Applications? Are we dragging the UnitySetup-Vuforia-AR-Support-for-Editor-2018.1.pkg installer there?

thx

 

Oh - I got it - the folder in the /Applications directory needs to be named "Unity" (not "Unity_2018.1.0f2" or whatever) - do this - then it will work - now to get back to work!

Thanks

 

Thanks, hackish workaround, but this fixed it for me.

 

I still can't understand how to install the new version, when Im using unity hub. Can you explain me how can I do it?

 

Having further complications with this issue where we initially made the project on windows Unity with vuforia, then working on it on a mac (to build to IOS) then noticed the issue was happening on an ipad air specifically with a black screen.. have tried all fixes such as installing the patch, using xcode 9.2 instead of xcode 9.3 .. we did however make a fresh project in unity on mac with the new patched vuforia that works so now we are porting ALL the contents of the original app to the new empty project that is actually working. I think this issue was caused by initially setting up the project on windows then trying to patch the vuforia plugin after.. however it should be the SAME plugin surely?

baffled.....

 

- After spending all day yesterday looking at the Xcode logs and removing things from the unity scene, the main cause of our issue is the UI Canvas component in Unity. Project works fine without a Canvas in the Unity Scene - as soon as we add one, the Vuforia camera renders black and the below Xcode log shows

I can confirm we are using 7.1.34, xcode 9.3 and unity 2018.1.0f1

I must stress that this issue appears to be specific to our Ipad Air models running IOS 11.3, our Ipad Pro and iPhone models on 11.3 run the app with no problems - using an iphone 6s, iphone 7 and iphone x.

Scroll to the bottom of the log to see the UIView conflicts

Xcode Log:
StartVuforia
UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:Log(Object)
Vuforia.VuforiaARController:StartVuforia(Boolean)
Vuforia.VuforiaARController:StartAfterInitializationCompleted()
Vuforia.VuforiaARController:UpdateState(Boolean, Boolean)
Vuforia.DigitalEyewearARController:Update()
System.Reflection.MonoMethod:InternalInvoke(Object, Object[], Exception&)
System.Reflection.MonoMethod:Invoke(Object, BindingFlags, Binder, Object[], CultureInfo)
System.Reflection.MethodBase:Invoke(Object, Object[])
System.DelegateynamicInvokeImpl(Object[])
System.MulticastDelegateynamicInvokeImpl(Object[])
System.DelegateynamicInvoke(Object[])
Vuforia.DelegateHelper:InvokeDelegate(Delegate, Object[])
Vuforia.DelegateHelper:InvokeWithExceptionHandling(Action)
Vuforia.VuforiaBehaviour:Update()

(Filename: /Users/builduser/buildslave/unity/build/Runtime/Export/Debug.bindings.h Line: 43)

cameraDeviceStartCamera
2018-05-11 08:53:49.516802+0100 gymsharkdemo[283:9907] ERROR/AR(283) 2018-05-12 08:53:49: VideoBackgroundConfig with screen size of zero received, skipping config step
2018-05-11 08:53:49.523841+0100 gymsharkdemo[283:10000] Deleting old image data @ 0x0
2018-05-11 08:53:49.523956+0100 gymsharkdemo[283:10000] Created new image data buffer @ 0x11b4a8000 w/ 1382400 bytes
Setting up 1 worker threads for Enlighten.
Thread -> id: 17174f000 -> priority: 1
2018-05-11 08:53:50.404819+0100 gymsharkdemo[283:10028] DEBUG/AR(283) UIView has CAMetalLayer layer class
2018-05-11 08:53:50.405214+0100 gymsharkdemo[283:10028] DEBUG/AR(283) UIView does not respond to selector renderFrameVuforia
2018-05-11 08:53:50.405349+0100 gymsharkdemo[283:10028] DEBUG/AR(283) UIView has CAMetalLayer layer class
2018-05-11 08:53:50.405389+0100 gymsharkdemo[283:10028] DEBUG/AR(283) UIView does not respond to selector renderFrameVuforia
2018-05-11 08:53:50.405422+0100 gymsharkdemo[283:10028] DEBUG/AR(283) Could not find a UIView with CAEAGLLayer or CAMetalLayer layer class that responds to selector renderFrameVuforia

Are any Vuforia or Unity devs looking at this thread to see this issue? It is affecting projects we are working on which have involved testing on an ipad Air

 

Further to my previous post, we have identified there is an incompatibility with the metal framework in this Vuforia patch version 7.1.34 where simply adding an empty canvas or anything requiring the metal framework causes the app to run with a black screen - the fix is to switch the graphics API to GLES2.0 only for your build to avoid this horrible scenario

Original user post on vuforia dev forums that brought it to my attention after scratching my head over it for a whole day or so :
" bringing more components into the scene along with ARKit seems to break it. I have a hunch that the Metal framework required by ARKit is the root cause of an incompatibility somewhere. When running only under only GLES2.0 the issue disappears. However in our case seeing as we need to have ARKit included there is no way around having the Metal framework available. I also had a look at whether the Canvas component could be causing the "VideoBackgroundConfig with screen size of zero received, skipping config step" issue during a resizing step, but this seems to work in isolation which leads back to Metal being the cause.

If anyone from Vuforia could enlighten us and give a timeline for a fix that would be great. "

 

Rob are you building in the cloud or locally? We're able to have a canvas object if we build locally on the latest everything... but cloud builds are black camera.

 

It is highly likely that cloud build is using the player settings option for Graphics API - Metal or Automatic graphics API.

You need to change it to GLES 3.0 or GLES 2.0 as there seems to be a compatibility issue between vuforia, unity UI and the Apple Metal graphics API on specific apple devices (in our office, this only affects the Ipad air and not Iphones or Ipad Pro

 

When upgrading a project from Unity 2017 to 2018.1.0f2, there are alarms related to databases coming from the Vuforia scripts. Please check the alarms below.

Assets/SamplesResources/VuforiaSamplesUI/Scripts/SamplesMainMenu.cs(127,31): error CS1061: Type `Vuforia.VuforiaConfiguration' does not contain a definition for `DatabaseLoad' and no extension method `DatabaseLoad' of type `Vuforia.VuforiaConfiguration' could be found. Are you missing an assembly reference?

Assets/SamplesResources/VuforiaSamplesUI/Scripts/SamplesMainMenu.cs(131,44): error CS0131: The left-hand side of an assignment must be a variable, a property or an indexer

Does anyone know how to fix this?

 

@Vuforia-Strasza Does Unity 2017.4.x not receive this vuforia update?

 

The issue is only resolved in 7.1.34 with Unity 2018.1 at the current time. A patch for 7.0 with previous versions of Unity is in the works and will be available in the near future.

 

I can confirm this. I even copied the newest folder from 9.4 and it worked great in 9.2!

I'm using Unity2017.4.2f2 for this for now.

 

Hello, I'm currently using Vuforia 7.3.8 from the early access program and Unity 2018.2.0f2 with XCode 9.4, I'm getting the same error, even if I build with XCode 9.2 or 9.3. I wonder if you guys fixed the error on the latest Vuforia version but not the one that it is in the early access section.

 

This is fixed in the current commercial versions of the SDK. Unfortunately the fix isn't in the current EAP build, but will likely make it into the next major update. The work around that I believe was described earlier in this thread should work for the EAP build as well.

Apologies for the inconvenience.

 

Hi there,
I am wondering if there is the same discussion about iOS 11.4, because this issue is still existing on this new OS version, with Vuforia 7.2.20 and Unity 2018.2.
Same error : [ videobackgroundconfig with screen size of zero received ]

Any idea ?

 

Hi,
I am working with Vuforia Cloud recognition using Unity 2017.3.0p4 Vuforia 7.0.47. I am having issues of Black screen on my iOS 11.3 build with Xcode 9.4. Also tried with Unity 2018.1.4f1 with Vuforia 7.1.43 but cloud recognition not working any more.

 

Hey, @Vuforia-Strasza

Any news on this?

Thanks!

 

I have found myself victim to this issue as well. It happened randomly... Everything was working fine when building to iPad to test the app, but after making a few updates in the app and reinstalling I now suddenly only see a black screen and everything seems to freeze. It also seems to freeze the Xcode application. The last thing I see in the console before it freezes is Rendering mode set to: OpenGL ES 2.0

iPad ios 10.3.3
Unity 2018.1.7f1
xcode 9.4

Help!

 

Same issue here.