Failed to install the application. Invalid XAP package signature or WP manifest file is invalid.

Question

I have a WP8 application that I need to build in 3 configurations (release, release (prepro), release (fake)). Each configuration point is different from another server and has different application icons. I need to have all 3 assemblies in the phone at the same time, so my solution is that I created 3 different WMAppManifest.xml (with different paths and icon tracks) and I will copy the correct code into the rebuild step . This works great (based on this article http://www.tonicodes.net/blog/using-different-wmappmanifest-files-for-release-and-debug-builds/ ).

I upgraded the application to WP81 Silverlight. There is an additional Package.appxmanifest file. So I created 3 different Package.appxmanifest files, setting the PhoneProductId attribute in the correct guide and adding a pre-build step to copy also for this file.

When I try to run the application in release (prepro) or release (fake), which means that different WMAppManifest.xml a Package.appxmanifest first copied to the project, I get

 Installation of the application failed. XAP package signature is not valid or the WP manifest file is invalid. Re-sign with valid signature and fix the manifest file. 

Is there anything besides PhoneProductId that I need to change in the new Package.appxmanifest files to get the job done?

Answer 1

I found what I need:

• Make package Package.appxmanifest> Identity> Name unique (according to @ kjo4jc answer )
• Change the GUID of the Package.appxmanifest mp: PhoneIdentity> package to be different from the value used in the repository.
• The changed GUID also needed to be changed in wmappmanifest.xml Deployment> App> ProductID to match.

Answer 2

I had the same problem and maybe I can help you. this hash signature is invalid, it happens when some of the "images" in the appxmanifest file are not actually in the project. I deleted the screen image that caused this error and deleted it from the appxmanifest file. In addition, for each package, you have a new package identifier if you want to publish the application that you receive in the dev center after registering your alias.

And there is a publisher ID, which you will also receive after renaming the application name, in this format "CN = ************ ".

And most importantly, and what I think you're looking for, you cannot install the same application twice on the same phone. I tried this and somehow it just doesn't work. I have an application from the store and I can’t install it from visual studio before I remove it from the store. It happened never before at 8.0

Answer 3

I found a very easy workaround. Just add "DEBUG" to the end of the current package name in the Package.appxmanifest constructor.

Then you can use the deployed version of debugging: just remove "DEBUG" from the package name before sending it to the repository.

In addition, if you have a WMAppManifest.xml file, add “DEBUG” to the display name so that you can easily distinguish what is on your phone.

Greetings.

Answer 4

I found this if you try to debug an application on a phone that already has a version of the application downloaded from the store.

The easiest way to fix it is to first disconnect the application from your phone.