Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to Sign Manifest #181

Closed
osbash opened this issue May 15, 2023 · 2 comments
Closed

Failed to Sign Manifest #181

osbash opened this issue May 15, 2023 · 2 comments

Comments

@osbash
Copy link

osbash commented May 15, 2023

We've been using this package for a little under a year and our apple certificate recently expired.

After generating a new certificate and following the instructions found here: https://github.com/tomasmcguinness/dotnet-passbook/blob/master/using-openssl.md

A new certificate was generated and replaced the existing one as well as downloading the G4 version of AppleWWDRCA. When running this locally, everything works fine. As soon as this is pushed to our production server, a "Failed to sign Manifest" error is thrown with no additional details.

I can confirm that the Pass Identifier, Team Identifier and Password are all correct.

The only thing that I did notice is when I run the working .pkpass (generated locally) through the pkpassvalidator everything passes except "PassTypeIdentifier in signature matches value in pass.json"

Any thoughts on this?

@tomasmcguinness
Copy link
Owner

tomasmcguinness commented May 18, 2023 via email

@tomasmcguinness
Copy link
Owner

Closing this as I haven't heard anything back. If you have more information, please reopen the ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants