Topic has a solution and is locked
Log in or register to post comments

Publishing Windows Store Unity Vuforia App not Supported

January 4, 2017 - 4:53am #1
Topic solved

Vuforia SDK Version: 6.2.6 -

Description with steps to reproduce: When publishing to windows store many errors are encountered during the Supported API test. The local WACK test passes.
Exemple of the errors are:

API cameraDeviceDeinitCamera in __internal.dll is not supported for this application type. Vuforia.UnityExtensions.dll calls this API.
API customViewerParameters_SetButtonType in __internal.dll is not supported for this application type. Vuforia.UnityExtensions.dll calls this API.
API eyewearUserCalibratorIsStereoStretched in __internal.dll is not supported for this application type. Vuforia.UnityExtensions.dll calls this API.

With the comment that
Using an API that is not part of the Windows SDK for Windows Store apps violates the Windows Store certification requirements.

I am following the official guide and using the sample project to test:
https://library.vuforia.com/articles/Solution/Developing-for-Windows-10-in-Unity
To package I am following https://msdn.microsoft.com/windows/uwp/packaging/packaging-uwp-apps

I am using Unity 5.5.0f3
Visual Studio community update 3.
Visual Studio Tools for Universal Windows Apps 14.0.25527.01)
For solution configuration select Master and for target platform select x86. (Master is a unity specific config setting the Compile with .NET Native tool chain to true in the project properties.)
When packaging I deselect x64 and ARM leaving only x86.
The local test passes with no issue WACK (Windows app Certification kit is installed (My version is 10.0.14393.33)
Then in the microsoft devcenter the app is set to publish manually and submited to the store.

After a while the Certification process fails in the Supported API test with 232 errors.

-

Development OS (Mac OS X, Windows, Linux): Windows -

Mobile OS and Version: Windows 10 -

Mobile Device Manufacturer and Model name: Microsoft (Surface Pro 4) -

Do the Vuforia Sample Applications show the same behavior?: Yes

Publishing Windows Store Unity Vuforia App not Supported

April 18, 2020 - 3:11pm #12

i still have this problem with version 9

Publishing Windows Store Unity Vuforia App not Supported

March 3, 2017 - 11:29am #11

Hello,

My understanding is that this issue was resolved in the 6.2 patch release: https://developer.vuforia.com/downloads/sdk

Thanks

Publishing Windows Store Unity Vuforia App not Supported

March 1, 2017 - 11:42pm #10

medabit wrote:

Hello,

We've been working with Microsoft of a very similar, if not the same, issue and were provided the following workaround:

Copy the Vuforia.UnityExtensions.dll into the UWP solution as __internal.dll, add it to the project as Content, and recreate the package.

This solved the issue and it passed WACK both online and locally. Basically, WACK sees that you are referencing a DLL (__internal) that is neither in the package nor a system one.

MS is working with the Windows Store team on the issue, as well.

Hope this helps.

Thanks.

 

can you give little more explanation about where to paste  the dll.

from unity to VS project?

need both __internal.dll and Vuforia.UnityExtensions.dll in Unprocessed folder?

Publishing Windows Store Unity Vuforia App not Supported

March 1, 2017 - 11:41pm #9

can you give little more explanation about where to paste  the dll. 

from unity to VS project?

need both __internal.dll and Vuforia.UnityExtensions.dll in Unprocessed folder?

 

 

Publishing Windows Store Unity Vuforia App not Supported

March 1, 2017 - 11:28pm #8

Have the same problem , i tried above mentioned method to copy and rename of Vuforia.UnityExtensions.dll. But still the same Error while certification.

Anyone got it working.

 

Publishing Windows Store Unity Vuforia App not Supported

February 22, 2017 - 8:19am #7

Hi guys,

I have the same problem, I tried to copy and rename the Vuforia.UnityExtensions.dll to __internal.dll and added it to the "Unprocessed" folder as content for the build action property. Is that what you did?

 

 

Publishing Windows Store Unity Vuforia App not Supported

February 7, 2017 - 7:41am #6

Hi guys,

faced the same problem with "ILT0039: Found two assemblies" error. 

I found a way that somehow worked for my HoloLens-Vuforia project:

After building in Unity (and selection of "Unity C# Project" in BuildSettings), the VS project  contained 3 projects: Assembly-CSharp-firstpass, Assembly-CSharp and YourProject_UWP. I copied and renamed __internal.dll and added it to the "Unprocessed" folder of YourProject_UWP within VisualStudio . It seemed like the location in the Unprocessed folder is important ?!

 

After doing that local and remote WACK worked for me.

Thanks for the initial advice of medabit

 

Publishing Windows Store Unity Vuforia App not Supported

February 6, 2017 - 6:13am #5

Hi @medabit could you tell me Where to add __internal.dll file and build. because i cant build after adding this dll to solution folder. it show me an Error

 ILT0039: Found two assemblies. Thanks in advance

 

Publishing Windows Store Unity Vuforia App not Supported

January 19, 2017 - 11:18pm #4

Hei, I am having the same issue. I added the dll into the project as __internal.dll.

But now it won't build, it says it found two assemblies with the same assembly identity.

I guess I did something wrong but the answer is not so clear (at least to me), maybe a quick visual explanation from a Vuforia representative would do.

 

Publishing Windows Store Unity Vuforia App not Supported

January 12, 2017 - 12:40am #3

Yes! This workaround solved it.

Worth mentioning is the proper way to add something as content in a Visual studio project is to rightclick a folder in solution manager select Add->Existing Item.

I copied the file into the project to begin with making it harder to deal with for myself.

 

Thanks!

Publishing Windows Store Unity Vuforia App not Supported

January 6, 2017 - 2:00pm #2

Hello,

We've been working with Microsoft of a very similar, if not the same, issue and were provided the following workaround:

Copy the Vuforia.UnityExtensions.dll into the UWP solution as __internal.dll, add it to the project as Content, and recreate the package.

This solved the issue and it passed WACK both online and locally. Basically, WACK sees that you are referencing a DLL (__internal) that is neither in the package nor a system one.

MS is working with the Windows Store team on the issue, as well.

Hope this helps.

Thanks.

Log in or register to post comments