I need help on code signing of my windows store app to deploy to target audience. When i try to change default certificate provided by visual studio at the time of Windows Store 8.1 project creation to my company certificate. Visual studio is throwing error
"The Manifest designer could not import the certificate.The certificate you selected is not valid for signing because it is either expired or has another issue. "
Is there any way for code signing in windows store 8.1 i see most of the blog targeted for windows 8. I need any info targetting in windows 8.1
My end goal is to deploy my windows store (LOB) without any developer license.
The certificate publisher name needs to match the publisher name defined in your app manifest. This means you will likely need to make a new certificate. You can, however, install the new certificate on your devices, including using something like a group policy (if they're all on the same domain).
We were getting that same error when trying to sign our packages with our existing code-signing certs. We resolved the issue by modifying our code-signing certificate template to include the "Basic Constraints Extension".
After changing the template and issuing a new certificate, we were able to sign the windows app package with the new certificate, and install the app on domain computers.
Here is the walkthrough that put us on the right path:
Side Loading Deployment of Windows Store Apps in Enterprises – Step by Step
We didn't exactly follow these steps... all we did was modify our template (as he does) and then requested a new certificate from the old certsrv asp page like we've been doing for years.
Related
I try to initialize Windows phone 8 application with Parse. I would like to use Push notifications. In the Parse's web settings are Package Security Identifier (SID) and Client Secret required. I am not able to find what should I insert into these two textboxes. Windows Phone application has only its own App ID...
Can you tell me what is the right way how to set the Windows phone application up?
Thank you.
Myth Rush
You are going to have to register your application with the windows store
The following documentation goes through how to do it for azure.. But the process should be the same fore you.
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-dotnet-backend-windows-store-dotnet-get-started-push-preview/
In the Windows Dev Center page for your new app, click Services.
In the Services page, click Live Services site under Microsoft Azure Mobile Services.
In the App Settings tab, make a note of the values of Client secret and Package security identifier (SID).
I have developed Windows Phone Silverlight application (support 8.0 and 8.1) for my client request. The client is goint to publish the application in WP app store, but first he must check on his phone if everything is OK with the application.
The application was developed with Visual Studio 2013, I've got developer account and own phone assigned to this account on which I have tested the application.
The question is, how can my client install the application on his own phone skipping windows app store? I have sent him builded *.xap file but he had a some problems with installation (Cannot install company application)?
You can submit your app to Windows Phone Store BETA. Your app will by certified quickly, and your client will be able to download it just like any other app from Store. The difference is that it will be visible and possible only for him.
Log in to you DevCenter account, click Submit App. Then, in App info section expand More options and select Beta. Then you can provide your client's mail.
I'm not sure, but I think that the name of the app should not be the same as the final version. So you can name it "My App Beta" to avoid future name conflict with the final version.
One more thing. When your app pass certification process, you have to send the link to the app to your client, because he won't get any notification.
We are trying to sign a Windows 8.1 Store application with a corporate certificate obtained from Symantec. The certificate was originally ordered for Windows Phone 8 application signing, but the same certificate should work for Windows 8.1 apps also.
On a fresh Hello World -project, when we try to choose the certificate from the manifest designer in Visual Studio 2013, an error message is given: "The Manifest Designer could not import the certificate. The certificate you selected is not valid for signing because it is either expired or has another issue. For more information, see http://go.microsoft.com/fwlink/?LinkId=241478."
The certificate is most certainly not expired. On the "another issue" angle, a common suggestion for a possible cause for this issue was a publisher name mismatch between the certificate and the application, but that has been ruled out. If we skip some signing checks by adding a EnableSigningChecks=false to the .csproj file, we can sign the app, but then another error is given by PowerShell when trying to install the application: "Error: The certificate can't have the following extended key usage: 2.16.840.1.113733.1.8.52.1." Only the Code Signing and Lifetime Signing EKUs are allowed."
We asked for help on this issue from Symantec and Microsoft, but they didn't know how to help with this issue.
Has anybody encountered a similar issue with signing their apps? Is there a solution to this problem?
This issue looks to be the same as in Choosing a certificate for a Windows Store application via the package.appxmanifest, where the solution was to get a new certificate. Is the only thing we can do to just buy a new certificate?
We are developing a company app for windows phone 8.
I have followed every step described in Company app distribution for Windows Phone
Here is what I did:
Registered company account
Bought an enterprise certificate from Symantec.
Exported PFX file with private key
Generated Enrollment Token (AETX file) from PFX.
Developed application, built with visual studio and get xap file
generated. (Name it App.xap)
Precompiled managed assemblies and Signed it with certificate using
BuildMDILXap.ps1 powershell script. (All messages indicated success).
Hosted AETX and signed XAP file on our web server.
At this point, when a wp8 phone tries to download XAP file without first installing AETX, The phone gives proper error message: "Before you install this app, you need to add XXXX company account. Contact your company's support person for help".
After installing AETX, when wp8 phone tries to install XAP file, the phone asks for confirmation: "Would you like to install App1 from XXXX?" After clicking "install" button, nothing happens. There is no success message, no error message, no indication of installation, and the application does not show in application list.
I have also tried sending AETX and XAP files over email (in case internet explorer or iis cannot handle file types), same result.
I have also tried doing the same for our company hub app, same result.
As far as I understand, company hub app is just another app (of course for different purpose) and both normal app and hub app can be distributed same way (over web address or email etc), right?
What is wrong? Cannot find the problem here?
Any ideas?
I bet you don't have a proper setup for code signing. One important step that is easy to miss is to install the parent certificates of your enterprise code signing certificate (that you got from Symantec). Specifically, download and import the following two certificates and then try to sign the XAP file again.
https://knowledge.verisign.com/library/VERISIGN/ALL_OTHER/Symantec_Enterprise_Mobile_Root_for_Microsoft.cer
https://knowledge.verisign.com/library/VERISIGN/ALL_OTHER/Symantec_Enterprise_Mobile_CA_for_Microsoft_Cert.cer
It is sad that the signing tool does not report any errors, yet the output is not a correctly signed XAP that WP8 would accept.
We are developing a company app for windows phone 8.
I have followed every step described in Company app distribution for Windows Phone
Here is what I did:
Registered company account
Bought an enterprise certificate from Symantec.
Exported PFX file with private key
Generated Enrollment Token (AETX file) from PFX.
Developed application, built with visual studio and get xap file
generated. (Name it App.xap)
Precompiled managed assemblies and Signed it with certificate using
BuildMDILXap.ps1 powershell script. (All messages indicated success).
Hosted AETX and signed XAP file on our web server.
At this point, when a wp8 phone tries to download XAP file without first installing AETX, The phone gives proper error message: "Before you install this app, you need to add XXXX company account. Contact your company's support person for help".
After installing AETX, when wp8 phone tries to install XAP file, the phone asks for confirmation: "Would you like to install App1 from XXXX?" After clicking "install" button, nothing happens. There is no success message, no error message, no indication of installation, and the application does not show in application list.
I have also tried sending AETX and XAP files over email (in case internet explorer or iis cannot handle file types), same result.
I have also tried doing the same for our company hub app, same result.
As far as I understand, company hub app is just another app (of course for different purpose) and both normal app and hub app can be distributed same way (over web address or email etc), right?
What is wrong? Cannot find the problem here?
Any ideas?
I bet you don't have a proper setup for code signing. One important step that is easy to miss is to install the parent certificates of your enterprise code signing certificate (that you got from Symantec). Specifically, download and import the following two certificates and then try to sign the XAP file again.
https://knowledge.verisign.com/library/VERISIGN/ALL_OTHER/Symantec_Enterprise_Mobile_Root_for_Microsoft.cer
https://knowledge.verisign.com/library/VERISIGN/ALL_OTHER/Symantec_Enterprise_Mobile_CA_for_Microsoft_Cert.cer
It is sad that the signing tool does not report any errors, yet the output is not a correctly signed XAP that WP8 would accept.