yes,

or you can just get rid of the sample UI stuff completely and create your own project with the Vuforia prefabs (not the samples); for example, a simple Imge target project can be setup by starting with a fresh new project and:

- drag ARCamera prefab into your scene

- remove MainCamera

- drag an Image Target prefab into the scene

- import Datasets, configure ARCamera and targets

- add augmention object to each Image target

etc.

see the developer guide for details about using Vuforia in Unity.

So for the time being, we can rename (refactor) the conflicting classes name in vuforia library and use it. right?

The Vuforia samples in the next release will include a fix for the UI naming conflict; however, the exact date of the next release is still not available. 

In the meantime, the workarounds suggested in this thread can be used.

Is there any solution to this problem yet or not???

If you need to keep the scripts in, when the three namespace errors pop up in unity open the first script in Mono and right click on the name, i.e. UIButton and find all references and go through each script ending. then saving scripts. 

Then backup and use for further projects so you don't have to go through the process again. Short term fix. 

Agree though, the scripts can be taken out and project can be built up manually.

+1 

Or even better, why not take out the UI stuff all together? Seems those elements are causing the trouble, while (as mentioned before) NGUI is pretty much becoming the standard for UIs. 

Or maybe post a way to disable/strip down the SceneManager/AppManager to just detect inputs?  

I do have a project which contains a previous example of the video texture, without the UI hoopla (just PlaybackBehaviour and Controller), which worked fine. 

Same here. This issue is causing a lot of extra script editing, trial and error in some cases. The bug in previous versions of Vuforia for Android platforms means that the latest version of Vuforia is the only version available to use, unless there's access to a previous and stable version. Using the most up to date SDK and NGUI is a nightmare. 

Is there an update for this namespace conflict? NGUI is basically the standard GUI plugin for Unity now... It would be really nice to have a fix. 

We are addressing this issue, yes, but I don't have any official dates for when the new samples may be released, at the moment.

Hi, 

Has there been any developments regarding this issue?

Noted that on the Playmaker forum one of the developers will be looking at a solution to a connected issue.

http://hutonggames.com/playmakerforum/index.php?topic=5817.msg28943#msg28943

Thanks

Did you resolve the file name changes by editing the Vuforia native files or NGUI?

I've tried following your instructions but still having the same issue as you discribed.

Any help would be most appreciated. 

Thanks for the report and for your suggestion; we will take this into consideration for a future update of the samples.

UIButton, UILabel, UIRect. It would be best if all of the UI classes had their own Namesapce or were prefixed with something, like "vf_"

Adam

Can you post the list of conficting references from your Unity console?

Same here, i had to change vuforia UIBUTTON and UILABEL class name to UIBUTTONQ and UILABEL Q and fix inside the script. It works now.

But would be great to have this fixed by Vuforia in a proper way, NGUI is basically the most used gui system in unity. 

Please fix this. NGUI is a veyr popular UI solution, and you have chosen naming conventions which conflict with NGUI's. Anyone who updates to the latest Vuforia will get stung with loads of errors, which are a nightmare to fix. Please fix this ASAP and release a new build.