locked
Certificate not showing up via "Select from Store" button RRS feed

  • Question

  • We have a code signing certificate that we want to use for signing our windows 10 UWP app.

    We have used this certificate successfully for Windows phone 8 apps. Now we want to use it for a Windows 10 UWP app but when we want to select the certificate from the Certificate Store then the certificate does not show.

    The message does not provide any information on why our certificate does not meet the criteria.

    How can we check what's going wrong?

    Any help would be greatly appreciated.

    Andy

    Monday, May 1, 2017 8:33 AM

All replies

  • The certificate is clearly not recognized:

    But the certificate was installed, was meant for code signing and the private key is available.

    The weird thing is that when we want to build a Phone 8 project there isn't any issue and the certificate is recognized and valid, but when we want to do the same for a W10 UWP app then the certificate doesn't show.

    Any suggestions??

    Regards,

    Andy


    Tuesday, May 2, 2017 7:35 AM
  • Hi Andy,

    You may follow Create a certificate for package signing to create a new certificate and install it in the Store Trusted Root Certification Authorities to see if it can appear in the "pick from certificate Store".

    Besides, you can also choose the certificate via "select it from file".

    You can also follow Sign an app package using SignTool to sign your package with SignTool.

    Best regards,

    Mattew Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Proposed as answer by Mattew Wu Monday, May 8, 2017 5:44 AM
    Tuesday, May 2, 2017 10:21 AM
  • Matthew,

    Thank you for your reply. We're now one step further.

    Now we get the following error:

    But now we can't seem to change the app manifest publisher name from "Identity Name="FieldAssist.FieldAssist10" Publisher="CN=Field Assist International B.V." Version="10.0.0.0" to

    “OID.0.9.2342.19200300.100.1.1=8870158, CN=Field Assist International B.V., OU=Field Assist International B.V.”

    Some further help would be appreciated.

    Regards,

    Andy

    Thursday, May 4, 2017 2:09 PM
  • Hi Andy,

    >But now we can't seem to change the app manifest publisher name from "Identity Name="FieldAssist.FieldAssist10" Publisher="CN=Field Assist International B.V." Version="10.0.0.0" to

    “OID.0.9.2342.19200300.100.1.1=8870158, CN=Field Assist International B.V., OU=Field Assist International B.V.”

    You can select Package.appxmanifest and click "F7" to view the code so that you can modify the value of Publisher to match it in certificate.

    Then you should be able to sign your package using the certificate.

    Best regards,

    Mattew Wu 


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    • Proposed as answer by Mattew Wu Thursday, May 18, 2017 9:00 AM
    Friday, May 5, 2017 8:22 AM
  • Thanks Mattew!

    That worked. Your help is greatly appreciated.

    Best regards,

    Andy

    Thursday, May 18, 2017 8:38 AM
  • Hi Andy,

    You might mark the response that helps to your question as answer so that other community member can also find it conveniently.

    Thanks for your understanding.

    Best regards,

    Mattew Wu


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, May 18, 2017 9:02 AM