I am trying to run a Silverlight 8.1 WP application through the Windows App Certification Kit and I get an error stating that the file is not a valid .xap file. I'm not sure why it is happening and not finding much about it other than one article that hints at a manifest issue. I am however able to take a dummy Silverlight 8.1 app and Certify that without error (it fails of course, but no error). The actual error is:
Failed to unpack 'xap file'. The file does not appear to be a valid xap package.
Does anyone out there know why this can happen or at least where in the manifest I might start looking?
The answer to this turned out to be an issue with the Microsoft SDK I was using. The way I figured this out is by attempting to upload the .xap file to the store even though I got that very vague error because I was still able to side load the application, so I knew to some degree the .xap file was valid. I got the following error.
The last two errors (2001) gave me more to go on, so I did some research and came across this SO post which pointed to an issue with the Advertising SDK. It turns out that the SDK I was using was adding 2 entries for some reason instead of telling me it was the wrong SDK. I used the one that came with VS 2013 Update 1, but for Silverlight, you need to use the one located here under Windows Phone 8.1 Silverlight Apps
After installing this package (make sure it is 8.1 and not 8.0), I referenced that SDK and all was well again.
Hope this helps someone else with this issue
For anybody else with similar problem, executing WACK on its own (not through VS command) runs smoothly.
Related
I'm developing an application windows phone 8.1.Previously, it worked fine on Windows Phone 10 and Windows Phone 8.1, but after one of the Windows 10 updates, the app is no longer installed from the Windows Store. The installation is crushed with 0x80073CF9 error. All I found about this error in the Google is advices for Win Phone users, not for developers. Logs obtained from the device indicates a crash during installation, it also did not help me.
I checked if there is in my project proscribed names, or library, rid of all warnings. Cleaned project. But nothing helps. According to the disgruntled responses of users I can see that they can not install it too. There is no errors while create package and publishing it to Store: this is the most confusing as it is not clear what went wrong and what hinders to install the application on the device.
I am developing in Visual Studio 2015.
Did someone face similar problems?
UPDATE
I tried all the tips have been found in Google including correction time and language settings, soft reset, hard reset and many others. Result still the same.
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.
I am trying to deploy my windows 10 uwp app to the windows store. I got a validated developer account and everything set up. My app packages have been built and passed all tests of the testing kit. Now I am trying to perform the last step: uploading to the store.
The problem is, that the "Upload App Packages..." is greyed out! I tryed to clean the project, selected the project to no avail.
Has anyone got an idea what the problem might be or how to further debug it? As there is not error message I am not certain what is wrong in the first place...
Thank you!
According to the documentation, this option merely opens the Dev center dashboard. Save yourself the trouble and open it directly in your web browser: https://dev.windows.com
To be honest, for some reason I don't even have this option in my Visual Studio (maybe it was removed in VS 2015?). I've always generated the packages from VS then uploaded them with the web browser, without any trouble.
Goto in Release Configuration and Check .net native tool chain and optimize code then create app package again (Don't forget to associate app to store first)
I am trying to submit a Windows Phone 8.0 xap file to the store. It uploads, after the upload it says "Analyzing package", then "An unexpected error occurred. Please try again later. If the problem continues, contact support."
I contacted Microsoft, they told me to clear the cache, history, etc. and try again. I emptied my browsers and restarted, but it didn't work. And I guess the problem is not really about the browsers, because they are able to upload the xap files but they don't get accepted by Microsoft's system.
I also tried an old xap file which was accepted by Microsoft before. I stil get the same error, so that's probably not about my packages.
I solved this problem after create fresh app using command line. And allocate that app name on app store. i guess there would be problem of Microsoft Server.
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.