Totally Blank Unity / Microsoft Store Build fails WACK tests
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
c# unity3d visual-studio-2017 app-certification-kit wack
edited Jan 1 at 7:48
MickyD
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
add a comment |
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
c# unity3d visual-studio-2017 app-certification-kit wack
edited Jan 1 at 7:48
MickyD
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54
add a comment |
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
c# unity3d visual-studio-2017 app-certification-kit wack
edited Jan 1 at 7:48
MickyD
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.
c# unity3d visual-studio-2017 app-certification-kit wack
c# unity3d visual-studio-2017 app-certification-kit wack
edited Jan 1 at 7:48
MickyD
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
edited Jan 1 at 7:48
MickyD
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
edited Jan 1 at 7:48
MickyD
10.7k63352
edited Jan 1 at 7:48
MickyD
10.7k63352
edited Jan 1 at 7:48
MickyD
10.7k63352
10.7k63352
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
asked Aug 16 '18 at 11:29
HaydnHaydn
1281110
1281110
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54
add a comment |
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54
add a comment |
1 Answer
1
active
oldest
votes
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
edited Jan 1 at 7:53
MickyD
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51875991%2ftotally-blank-unity-microsoft-store-build-fails-wack-tests%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
edited Jan 1 at 7:53
MickyD
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
add a comment |
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
edited Jan 1 at 7:53
MickyD
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
add a comment |
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
edited Jan 1 at 7:53
MickyD
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."
edited Jan 1 at 7:53
MickyD
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
edited Jan 1 at 7:53
MickyD
10.7k63352
edited Jan 1 at 7:53
MickyD
10.7k63352
edited Jan 1 at 7:53
MickyD
10.7k63352
10.7k63352
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
answered Aug 19 '18 at 9:49
HaydnHaydn
1281110
1281110
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
add a comment |
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Wow, seriously?
– Adrian K
Feb 5 at 18:49
Yes, seriously.
– Haydn
Feb 5 at 23:04
Yes, seriously.
– Haydn
Feb 5 at 23:04
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
I submitted my WACK failing app to the MS Store - it seems to have passed validation (on upload), we'll see how the rest of the submission goes.
– Adrian K
Feb 6 at 5:07
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Yeah, Should be interesting, Let me know which version you are using, if it passes.
– Haydn
Feb 6 at 6:39
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
Successfully published in the store. My version info here, in the question: stackoverflow.com/questions/54489028/…
– Adrian K
Feb 7 at 3:59
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f51875991%2ftotally-blank-unity-microsoft-store-build-fails-wack-tests%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the same problem on VS2017 Community 15.9.4
– MickyD
Jan 1 at 7:54