I'm trying to pass WACK tests, but have problems with some tests. One is very strange for me:
App launch tests
Error Found: The app launch test detected the following errors:
Failed to launch App.
Impact if not fixed: An app that fails to launch presents a poor user experience, and will not be accepted by the Windows Store.
How to fix: Investigate and debug the app to identify and fix the problem.
I really don't know where is the problem. I tried to run tests on empty project or another app installed from windows store, but had same result. I used this instruction
http://msdn.microsoft.com/en-us/library/windows/apps/hh694081.aspx
Related
Whenever I am starting to test an Windows Phone app (even a blank app) on emulator, I am getting error "The project needs to be deployed before it can be started". The emulator will be started & run successfully, still no luck in deploying app on emulator. Getting error DEP6100 & DEP6200.
These are the stuffs I tried till now:
Checked "deploy" option in 'Configuration Manager'.
Tried deploying Windows 10 Mobile, Windows Phone 8.1 & Windows Phone 8 blank apps on different types of emulators.
Although I am able to run apps on my device.
I am running Visual Studio Enterprise 2015 on Windows 10 Enterprise.
The Emulator is x86 based and Phone is ARM architecture. To run the app in the emulator, change the CPU to x86 in the toolbar and compile it. Now you can deploy te App to the Emulator and test it.
I faced problem like that and I fixed it by right click on project > properties > change platform target to X86.
I just started playing with Xamarin Forms, and ran into this error after following the Xamarin Forms Quickstart Guide. The error message actually said to Run the Deploy... for the project that you are trying to run. Deploying the project seems to install some Windows dependencies that might be required to run the UMP. After deploying the project, it ran without issue as a Windows Desktop app, or if you change to Device, then install emulator, as Windows Phone app.
This error was relentlessly happening to me as well, and I found out that it was because my project was saved on a SanDisk SD card. If I simply moved the entire solution to my C drive, it built without issue, but on the D drive, it would give this error.
Getting the following test failure while running Windows App Certification Kit 10.0:
Platform version launch
Error Found: The high OS version validation detected the following errors:
Cannot launch App
The app <apppackagename> failed platform version launch test.
Impact if not fixed: The app should not use version information to provide functionality that is specific to the OS.
How to fix: Please use recommended methods to check for available functionality in the OS. See the link below for more information.
Any feedback on how to resolve that issue appreciated.
You need to update your Windows App Certification Kit to the latest version and then update the "Target version" inside the solution's properties to the latest windows build version (2004).
Now Create app package again and you will be OK :)
I have deployed my UWP application to windows store successfully. It rans perfectly in windows phone, however, when installed in pc / laptop from windows store, it fails and crashes.
checking event viewer (windows log) shows below error;
Activation of app
AppName!App failed with
error: The remote procedure call failed. See the
Microsoft-Windows-TWinUI/Operational log for additional information.
I didn't understand what kind of error it is?
Thanks!
Have you tried yourself, with Visual Studio 2015, to run it on a Windows Phone device in Release Mode ?
Most of time, this kind of errors are due to .NET Native, which is not activated by default on Debug build but which is activated when app is published on the Store.
Thanks,
Does your app reference a portable project? If yes, does the referenced project include resource files? We have encountered similar issues and they were related to resource files. Everything worked nicely when the app was manually deployed but when downloaded from Store, the app just didn't work.
Turns out the problem was with the resource files which were inside referenced project. The problem was solved by copying the resource files from the referenced project into the app's project.
Its saying "The project needs to be deployed before it can be started.
Verify the project is selected to be deployed or deploy it explicitly by clicking one of the deployment commands in the Build Menu."
I have tried to explicitly deploy it from the build menu but its all in vain. Not able to understand whats wrong.
It may be caused by the fact that no devices are detected.If you try to debug on a real device, it may no be detected by your computer or VS. If you use the emulator, it may be an error with the emulator (like for example, the emulator doesn't launch, so you can't deploy on nothing).
Try removing Apache Cordova Tools Package.
Worked for me.
I have a Windows Phone 8.1 project that refers to a Windows Runtime Component, which exposes some other native projects of mine. The problem is I get a System.IO.FileNotFoundException when running it on emulator. However, if I catch the exception and check exception.FileName, it's null.
The guy here has mentioned he used ProcMon to figure out which file was missing. How do I use ProcMon to monitor file accesses made by an emulator? I tried monitoring the emulator process itself, but that didn't produce any info.
There is no way provided to run desktop apps such as ProcMon on the emulator. The linked post was able to run ProcMon on Windows, not on Windows Phone.
Your best bet is to debug the app running on the emulator. Use the unmanaged debugger so it can break in the native code, break on the first chance exception, then see where in the stack this is called from. Once you know where the problem is, you can set a break point at the beginning of the function then either step through or set a trace point to see what files are being used and what the app thinks it is doing then.