Maybe you need to start Unity with administration permission. That's the case for us when we update Vuforia.

Same issue here. During upgrade of Vuforia license agreement was accepted. But when launching through an android app it says "The Vuforia Developer Agreement needs to be accepted before using Vuforia in an application." and the camera is not available. What to do?

Upgrade of Vuforia already asked for administrative permissions. Starting Unity with administrative permission doesn't help as the update is already applied. Is it possible to re-accept the license agreement?

Hi all, it should be sufficient to just accept the license once per Vuforia version and machine.

Please help us debugging this issue if that does not work for you - we haven't seen this in the testing on our side:

• Are you seeing this on Mac OSX or Windows?
• Are you seeing the license popup every time you open the Unity project?
• If you are seeing it every time, please:
  • Accept the license
  • Close Unity
  • Please send us:
    • The exact Unity version you are using
    • The full Editor log from ~/Library/Logs/Unity/Editor.log
    • From your Unity project, the manifest.json from the Packages folder
• If the license popup is not shown, but you still can't start play mode or build the app, please:
  • Select Help -> Vuforia -> Show Developer Agreement from the menu
  • Does that trigger the license popup or open the license agreement in a browser?

Many thanks!

Vuforia Engine Support

Same issue too.

• I'm on a Windows platform
• The license popup does not show when Unity starts
• Showing Developer Agreement from the menu just triggers the license agreement in a browser

Edit : after further tests, I had to downgrade my Vuforia version from the latest (7.5.26) to 7.5.20 or older and run Unity as Administrator to make the message disappear.

I'm having the same issue when using Cloud Build. In Editor works fine, even "Build and Run" works (for Android at least) but with the cloud build, the camera stays black. Looking at the ADB debug reveals the "The Vuforia Developer Agreement needs to be accepted before using Vuforia in an application." message.

I have no idea where I should accept this message. The link to the agreement opens the agreement alright, but nothing else happens.

mediamonks wrote:

I'm having the same issue when using Cloud Build. In Editor works fine, even "Build and Run" works (for Android at least) but with the cloud build, the camera stays black. Looking at the ADB debug reveals the "The Vuforia Developer Agreement needs to be accepted before using Vuforia in an application." message.

I have no idea where I should accept this message. The link to the agreement opens the agreement alright, but nothing else happens.

We got the same problem on Unity Cloud Build for Android and IOS. We were using Vuforia 7.2.24 when we got this issue, then switched to Vuforia 7.5.26 and still getting the same error...

"Vuforia will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia -> Show Developer Agreement."

This error doesn't occur when building the project for Android in editor and the camera is working fine on our devices. We haven't tested building for IOS in editor yet.

We are using Unity 2018.2.13f

Hi all,

Unfortunately, due to the way how Vuforia is integrated in Unity today, we currently don't support Cloud Build.

For local builds, the previously seen issues with not being able to accept the EULA should now be resolved with 7.5.26.

Please ping us in case you are still seeing any issues like that.

Thanks,

Vuforia Engine Support

That's mighty disappointing. :-(

Besides, I can remember being able to create a Cloudbuid for a Vuforia project before so my guess is that Vuforia changed the way they handle the dev license and this is what broke cloud build. Hence the release note "Fixed an issue where EULA acceptance would not persist in some edge cases".

Hi there,

We are having the exact same issue, and a deadline looming, We can ofcourse do local builds (i`m on a mac) but it probably means build for IOS, then change the buildsettings to Android which takes an insane amount of time... (Correct me if i´m wrong... if you can ;))

Anyway, can you give an estimate when this will be fixed?

Thanks in advance.

Oh no.... we are actually disappointed after hearing this news... Because it affects significantly on our workflow. Since you put "currently", I assume that this is only temporary? If so, is there any estimate that the support will be up again? If not, is there other ways that can act as an Unity cloud build alternative apart from building our apps locally (e.g. other CI/CD tools) ?

Hello,

Everything was working fine in our setup till OCT 26, 2018 and suddenly broke because of this and we have to rebuild our system.

Seems like you made life of your honest users harder.

I can't understand how Vuforia can be integrated with Unity and not support cloud build.

I have a similar issue. I'm using Unity 2018.2.14f1 Personal with Vuforia 7.5.26. I am using Unity Cloud Build. This is the error I get:

ERROR: Vuforia will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia -> Show Developer Agreement".

I have clicked on: "Help -> Vuforia -> Show Developer Agreement" and as previously stated by someone else, it simply takes you to the Vuforia developer agreement in a web browser and when I attempt a rebuild, it still gives me the same error!

Question: How does clicking on "Help -> Vuforia -> Show Developer Agreement" make any difference to my build? (I was logged in at Vuforia when I did)

I also created a new Vuforia App License Key after clicking on: "Help -> Vuforia -> Show Developer Agreement", copied and pasted it in the Vuforia Configuration panel in Unity and rebuilt on Unity Cloud Build with the same error!

This is very frustrating. Please will someone fix this. Thank you kindly in advance.

I can confirm that this keeps happening when using Unity Cloud Build.

Are you serious about this?! We use only Unity Cloud Build (this is what cloud building is for, to not have to do local builds) for doing our versions and this breaks all of our AR projects we are doing with Vuforia.

It wouldn't be such an issue if it never worked, but until the recent versions it did. Now it is showing "ERROR: Vuforia will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia -> Show Developer Agreement"."

I'm pretty sure that this shouldn't be a big issue to fix, so please make this work again.

Hello,

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

• Cloud Build is currently only supported for the Vuforia versions that come packaged with a Unity Editor installation.
  • If you upgrade the version of Vuforia in an existing Unity installation via an upgrade installer (the one downloaded from the Vuforia Engine upgrade notifications in the Editor), it will only upgrade the Vuforia version on your machine and the Unity Cloud Build servers will build against an older version of Vuforia (which can cause all sorts of issues, mostly linker errors). We are working with Unity for a solution to this. It will most likely require us to change the way how we roll out new Vuforia versions for existing Unity installations, so this fix is a bit further out.
• There was a regression introduced with Vuforia 7.5 that broke cloud build, related to accepting the EULA
  • We fixed this issue with our 7.5.26 patch release. However, because of the previous issue, you’ll need to wait for the first Unity Editor version that packages the Vuforia Engine SDK 7.5.26 version out of the box. This version is Unity 2018.2.17, which should be available publicly next week.

So with Unity 2018.2.17, Cloud Build should work again, and we continue to work on a solution that allows upgrading Vuforia independently of Unity while still being able to use Cloud Build.

Apologies for the inconvenience and we'll keep this thread updated with relevant details.

Thanks,

Vuforia Engine Support

medabit wrote:

So with Unity 2018.2.17, Cloud Build should work again, and we continue to work on a solution that allows upgrading Vuforia independently of Unity while still being able to use Cloud Build.

Unity has now been updated and Cloud Build looks to be using the latest version, 2018.2.17f1, as confirmed by the build log.

Our project is using Vuforia 7.5.26, as confirmed by the '/Assets/Vuforia/version' file in our project.

However, we are still receiving the error:

'599: [Unity] ERROR: Vuforia will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia -> Show Developer Agreement".'

Can you provide any further update or suggestions on how to resolve this issue?

Thanks

Hello @swhite432,

Unfortunately, we're not sure why this issue is occurring in 7.5.26. We discussed the solution with Unity and both sides agreed that we had the correct approach to resolve. Now that the release is public, we'll continue debugging with the Unity team.

If anyone else can confirm that the cloud build fix in 7.5.26 works, or still doesn't work, please post to this thread.

Thank you and apologies for the inconvenience.

-Vuforia Engine Support

Currently, on iOS only, we are seeing 2 errors in the cloud build that are failing the build:



ERROR: Vuforia will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia -> Show Developer Agreement".



and



1951: ▸ ❌;  ld: '/BUILD_PATH/OUR_PROJECT_NAME/temp.XXXXXX20181129-5454-19k66kr/Frameworks/Vuforia.framework/Vuforia' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. file '/BUILD_PATH/OUR_PROJECT_NAME//temp.XXXXXX20181129-5454-19k66kr/Frameworks/Vuforia.framework/Vuforia' for architecture armv7

1952: ▸ ❌;  clang: error: linker command failed with exit code 1 (use -v to see invocation)



Unity Version: 2018.3.0b12

Vuforia Version: 7.5.26



Local builds are working fine in the same versions. Please keep us updated on the status of this issue.

Hi,

Any update on this error because i get this error using Vuforia 7.5.26 and Unity 2018.3.

[Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/VuforiaEditorScripts.dll

43: [Unity] Assets/Vuforia/Editor/Scripts/OpenSourceInitializer.cs(53,38): error CS0535: 'OpenSourceInitializer.DefaultBehaviourAttacher' does not implement interface member 'IDefaultBehaviourAttacher.AddDefaultModelRecoEventHandler(GameObject, ModelTargetBehaviour)'

44: [Unity] Assets/Vuforia/Editor/Scripts/OpenSourceInitializer.cs(53,38): error CS0535: 'OpenSourceInitializer.DefaultBehaviourAttacher' does not implement interface member 'IDefaultBehaviourAttacher.AddDefaultModelRecoEventHandler(GameObject, ModelTargetBehaviour)'

[Unity] -----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/VuforiaEditorScripts.dll

267: [Unity] Assets/Vuforia/Editor/Scripts/OpenSourceInitializer.cs(53,38): error CS0535: 'OpenSourceInitializer.DefaultBehaviourAttacher' does not implement interface member 'IDefaultBehaviourAttacher.AddDefaultModelRecoEventHandler(GameObject, ModelTargetBehaviour)'

268: [Unity] Assets/Vuforia/Editor/Scripts/OpenSourceInitializer.cs(53,38): error CS0535: 'OpenSourceInitializer.DefaultBehaviourAttacher' does not implement interface member 'IDefaultBehaviourAttacher.AddDefaultModelRecoEventHandler(GameObject, ModelTargetBehaviour)'

[Unity] ERROR: Vuforia Engine will not initialize. You need to accept the Vuforia Developer Agreement from "Help -> Vuforia Engine -> Show Developer Agreement".

Greetings,

Mark

Getting the same error as @multimediamarkers using Cloud Build using Unity 2018.3 and Vuforia 7.5.26 with a paid Vuforia License. 

Can you give us an update? What version of Unity Cloud Build works with 7.5.26? Or do we have to update to 8.0.10? 

I need an urgent fix...

We have verified that cloud builds are supported when using Unity 2018.3.4f1 (which includes Vuforia 8.0.10).

Any Unity version that includes 7.5.26 should work as well, but only the versions above have been verified explicitly.

There are two common pitfalls that need to be taken care of:

• When using cloud builds, you need to use the Vuforia version that came with Unity out of the box.
  
  You cannot patch your local Unity installation to a newer version of Vuforia.
  
  We are working with Unity to resolve this restriction in an upcoming version.
• The Vuforia developer agreement needs to be accepted on at least one local development machine.
  
  Accepting the agreement will result in a change to your Assets/Resources/VuforiaConfiguration.asset
  
  This change needs to be uploaded to your project repository before starting the cloud build.
  
  Failure to do so will result in exactly the error message posted below.

Thanks,

Vuforia Engine Support

Thank you for clarifying, Johannes!

I just want to note that my version control doesn't see any changes happen to the VuforiaConfiguration.asset

so either it has already been accepted in the past, or it's not registering that I've opened the developer agreement. 

Could you clarify what exactly has to be changed in the asset for it to work in the cloud build? If it helps, I can send you my VuforiaConfiguration.asset. 



 

Thanks for the follow up UcanJ.

Yes, please send me your VuforiaConfiguration.asset file, plus the exact version of Unity and Vuforia that you are using.

Thanks,

Johannes

I am NOT using Cloud Recognition or Cloud Build. I am trying to publish the new version of the app with the commercial Vuforia license to Play Store.

It builds/runs fine on most devices. But fails with Vuforia Developer Agreement error message on single device Google Pixel 3XL, which runs Android 10.

Deploying directly from Unity runs fine on that same device. Downloading/installing from Play Sore doesn't.

I use expansion OBB file and create APK for each platform.

My Unity is 2018.3.11

Vuforia 8.1.10

Any help will be appreciated

Thank you.

Has there been a fix to this in Vuforia 8.3 or Vuforia 8.5? 

I'm running into the exact same issue as schiegg's post right before.

1) Not using Cloud Recognition or Cloud Build

2) Runs fine on most devices, but seeing Vuforia Developer Agreement error on Pixel 3 running Android 10

3) Using expansion file OBB with split architecture builds to create 32-bit APK and 64-bit APK

4) Built with Unity 2018.4.2 and Vuforia 8.1.10

5) Problem only occurs with Google Play distributed builds though Internal/Alpha/Beta/Production tracks

Overall the Google Play distributed build on the Pixel 3 w/ Android 10 seems to be running into I/O related issues like other SDK config files fail to load so I'm wondering if Vuforia is running into a similar issue with whatever license file gets loaded.

Same issue with Vuforia 8.1, Unity 2018.3.8.f1.

Tested on Pixel 2 XL by using an internal test build that was uploaded to Play Store and has OBB. I am loading the image targets DAT/XML file manually post application load.

On direct deployment through USB things work as expected.

Is there any thing that needs to be done to accept some Developer License ?

Hi,

Tt seems that the issue occurs as Vuforia is initialized before the OBB is loaded. With 8.6 you will get a warning regarding this and our advise would be to first load the OBB file and only afterwards initialize Vuforia.

Thank you.

Vuforia Engine Support

I don't know if this was the correct way of solving the problem or not. But I changed the package name to get problem fixed.

Initially my package name was com.company.product.variation which I changed back to com.company.productvariation. Can't be sure but if the extra '.' may be cause the OBB file to not read correctly during the loading process ?

This allowed me to test the OBB routine locally as well as worked correctly when uploaded to store for Beta testing.

Thanks for All the Help.