Unable to open pkpass on an iOS device

[VyasRR]

Unable to open pkpass on an iOS device

[joe-keane]

Hi,

Seems like you have to fix passTypeIdentifier and set it with the same id that you did configure Developer portal.
Also you're setting the webServiceURL to an Apple URL http://ocsp.apple.com/ocsp3-wwdr01

[VyasRR]

Hi Joe,

I have changed the passTypeIdentifier but still I am facing the same problem. This time I removed the webServiceURL because I dont require my pass to hit any URL (also, I read in many blogs saying that webServiceURL and authenticationToken is not mandatory).

Attaching my new pkpass again.

IndyCar.zip

[joe-keane]

Hi Vyas,
The fields must be unique, you've several of them called "date".

[VyasRR]

Thank you so much. Your answer resolved my issue.

But while I try to deploy the code on IIS server, I am getting a weird error "The recipient certificate is not specified".

[joe-keane]

Hi Vyas,

I'm glad I did help.

Around the new error I'm sure if it's passbook related or something with certificates.
Can you provide more context around the message?

[VyasRR]

I deployed my website in the IIS present on Windows 2012 R2 machine. While the code hits the ComputeSignature line, I am facing the error "The recipient certificate is not specified".

The code runs perfectly on visual studio and the problem i am facing is only with the deployed code.

Below is the piece of code I am using for computing signature against the manifest:

private byte[] signit(string manifest, X509Certificate2 ourcert)
        {           
                byte[] manifestbytes = ASCIIEncoding.ASCII.GetBytes(manifest);

                ContentInfo contentinfo = new ContentInfo(manifestbytes);
                SignedCms signedcms = new SignedCms(contentinfo, true);

                X509Certificate2 appleWWDRCA = new X509Certificate2(currentDirectory + @"AppleCerts\Apple Worldwide Developer Relations Certification Authority.cer");

                CmsSigner oursigner = new CmsSigner(SubjectIdentifierType.IssuerAndSerialNumber, ourcert);
                //CmsSigner oursigner = new CmsSigner(ourcert);
                oursigner.IncludeOption = X509IncludeOption.EndCertOnly;

                oursigner.Certificates.Add(appleWWDRCA);

                oursigner.SignedAttributes.Add(new Pkcs9SigningTime(DateTime.Now));

                signedcms.ComputeSignature(oursigner);
                return signedcms.Encode();           
        }

[joe-keane]

I'm not entirely sure about it, but could be permissions or certificates related otherwise it won't run also on your machine.
Do you want to create a small sample with it?

[tomekdomek]

Hi, I am running the same issue that I cant open the passes on Iphone but on MAc it works fine. I looked on every thing which was written here but it just dont open.

[joe-keane]

Hi @tomekdomek, did you check the logs while opening? Can you provide a sample file?

[tomekdomek]

Here you go.Thank you.
I made the pass without
Can upload the file. I uloaded it on my server.
www.pbooking.de/passbook.zip

[joe-keane]

Here you go: ": Invalid data error reading pass pass.cbooking.de/4efc0224-c134-4b48-a27e-9cb63dcb57f1. Unable to parse relevantDate 2016-04-08T09:16:45.0789286+02:00 as a date. We expect dates in "W3C date time stamp format", either "Complete date plus hours and minutes" or "Complete date plus hours, minutes and seconds". For example, 1980-05-07T10:30-05:00."

If you plug the device to your mac the Devices logger will show you what's going on.

[tomekdomek]

Oh ok thanks. You recommand XCode for that.

So I guess the codebase is wrong because I set it by property of class PassGeneratorRequest and he rechanges it to that format.

[joe-keane]

You're right, the issue was introduced with this change:
writer.WriteValue(RelevantDate.Value.ToString("o"));
Will need to take a look into a proper fix.

[tomekdomek]

Can you give me the line how it should be so I can change it?
Ok I got writer.WriteValue(RelevantDate.Value.ToString("yyyy-MM-ddTHH:mm:sszzz"));​

[joe-keane]

@tomasmcguinness I'm planing to take a look into it today regarding the comments from @tuler at #45 and #46