I have just downloaded latest Unity 5.2.1 so I can publish game as Universal App. I am following steps but I got stuck on 12. Building goes fine but on verification I get:
You have to use Master build and .NET native in order to submit application to the store. All of these errors would happen if you did not.
Thank you both! Since I had it already set to Master build I assume upgrading to 5.2.1p3 was necessary. This time it passed.
Whoops I saw your reply just after I deleted my post to not be confusing. I'm all good now with the API with Master!
I forget to update. I got it work. Just always build to empty folder. After that open in visual studio and enable .NET native.
L’API ExecuteAssembly présente dans uwphost.dll n’est pas prise en charge pour ce type d’application. Adventure Of Wati.exe appelle cette API. L'API DllGetActivationFactory dans uwphost.dll n'est pas prise en charge pour ce type d'application. Adventure Of Wati.exe a une exportation qui transfère vers cette API. L’API OpenSemaphore présente dans api-ms-win-core-synch-l1-1-0.dll n’est pas prise en charge pour ce type d’application. System.Threading.dll appelle cette API. L’API CreateSemaphore présente dans api-ms-win-core-kernel32-legacy-l1-1-0.dll n’est pas prise en charge pour ce type d’application. System.Threading.dll appelle cette API.* Unity 5.3.4f1 certification fails
I have recently run into this issue on Unity 5.4b. My app is being built with Master config and .net native is enabled. I only receive the one error. Please advise. Thank you.
If someone else runs into the problem I was having, it appears to have been because I had "Unity C# Projects" checked in the build settings. All is working fine now.
@Tautvydas-Zilys Is .NET Native really a requirement to release a Unity App to the Windows Store? If so, why isn't this mentioned anywhere (tried googling)? I'm using the library "DOTween" and I can't build using .NET Native because of the issues with exceptions thrown can't be handled on the native side and thus cause crashes (or something like it, see: http://forum.unity3d.com/threads/uw...g-a-new-scene-in-master-configuration.401365/). Can you think of any solution to my problem? Thanks!
If you disable .NET Native, you simply won't be able to pass WACK... that's why you won't be able to submit your game. You can always target Windows SDK 8.1 or Windows Phone 8.1 where .NET Native didn't exist, but that's only a temporary solution... When MS stops accepting such applications, you'll stumble into this problem again
With latest Unity 5.4p3 targeting Universal 8.1 Windows I now get: Error Found: The supported APIs test detected the following errors: API setUnityPurchasingCallback in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingAddTransactionObserver in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingFinishTransaction in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingPurchase in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRefreshAppReceipt in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRestoreTransactions in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRetrieveProducts in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unitySetGroupId in tizenstore.dll is not supported for this application type. Stores.dll calls this API.
Hi, There was an update to IAP (1.8.1) released yesterday afternoon that should resolve this issue. The IAP section of the Services tab should be showing an Update button to get it installed. I don't think this update has made it to the Asset Store yet but will also be available there soon.
It fixed the Universal 8.1 error but now it has a Universal Windows 10 errors: Error Found: The supported APIs test detected the following errors: API D3D12GetDebugInterface in d3d12.dll is not supported for this application type. UnityPlayer.dll calls this API. API OpenSemaphore in api-ms-win-core-synch-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API. API CreateSemaphore in api-ms-win-core-kernel32-legacy-l1-1-0.dll is not supported for this application type. System.Threading.dll calls this API. API ExecuteAssembly in uwphost.dll is not supported for this application type. Frutakia 2.exe calls this API. API DllGetActivationFactory in uwphost.dll is not supported for this application type. Frutakia 2.exe has an export that forwards to this API.
Both Tizen Store and Samsung Galaxy Apps should work well with IAP 1.8.1. Please let us know in the IAP Forum if you encounter any difficulties.
The report is ok now but I submitted the app to the Windows Store and they send me an email saying after review its not-compliant for these reasons: Supported APIs Error Found: The supported APIs test detected the following errors: API setUnityPurchasingCallback in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingAddTransactionObserver in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingFinishTransaction in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingPurchase in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRefreshAppReceipt in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRestoreTransactions in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unityPurchasingRetrieveProducts in tizenstore.dll is not supported for this application type. Stores.dll calls this API. API unitySetGroupId in tizenstore.dll is not supported for this application type. Stores.dll calls this API.
Maybe I uploaded this (Windows 10 Universal) with the older IAP, the report was ok. Will upload again and see what happens.