"Cannot install enterprise application" on Windows Phone 8

Question

I developed an enterprise application for Windows Phone 8 and followed all the recommended steps to configure it for installation. I have a Symantec code signing certificate, and I created my application registration token and signed XAP, which I put in the OneDrive public folder. I created XAP using the BuildMDILXap.ps1 script that worked without errors. I did not bother using the company’s hub application, as we distribute only one application.

AET downloads OK on the phone and asks if I want to add a workstation account. I click "add", the dialog box disappears and no error occurs. There is no confirmation message, but I do not know whether to expect it.

When I download XAP, I get the message "Cannot install the application for the company. There is a problem with this application for the company. Contact a support specialist for help."

The phone was unlocked by the developer (which, of course, is not necessary), and I had an application loaded with sideways and working on it successfully earlier. However, it was deleted before attempting to complete the above.

I'm not sure what to do next. I tried to recompile and overwrite XAP and re-create AET, but nothing works.

Answer 1

After a fruitless attempt to solve this problem, I found a workaround that does what I need.

Turns out you can publish apps to the public app store but hide them from searching , essentially making them private to everyone who has no link. This solves my first problem by getting an application published in such a way that my client can access without me in order to have developer licenses for each of them. phones.

the disadvantage with this solution is that you still have to wait a few days for the update to be approved, which is not the biggest when you are still beta testing and need to make quick changes. However, Microsoft also has a beta version for Windows Phone applications. By designating the application as beta, the transfer takes place automatically within 2 hours , but you must restrict access to certain Microsoft accounts. The latter is not a problem, because the number of devices using the application is relatively small.

This eliminates the need to store a corporate application store in my case and saves the expense of the certificate and tinkers around it.