Closed dylanbeattie closed 2 years ago
Hey,
Are you using an older pfx file, one that was generated before the G1 -> G4 change?
I suspect the wording of my documentation maybe at fault here.
Ah - yes, I am! That would explain it.
So the fix is to create a new PFX file, which will now be signed with the G4 cert from Apple because.... that's just a thing now?
I presume Apple will honour the G1 until it expires next year.
You can just use G1 WWDR with your current PFX file and all should be right with the (passkit) world.
Yeah, that's what's working right now. I also discovered along the way that you get exactly the same (useless) error message "Sorry, your Pass cannot be installed to Passbook at this time" if you're serving PKPASS files over an HTTPS connection with an invalid certificate... ah, fun & games.
I've update the README with guidance around which WWDR cert and the cutoff times. Glad it's working!
I've updated to the latest 3.0.1 release of dotnet-passbook, and noticed you've amended the docs to specify that you have to use the "G4" version of the certificate...
G4 isn't working for me, but the original G1 version still works fine:
I'm now wondering if there's some undocumented dependency between the PFX file used as the passbook certificate and the version of the WWDRCA certificate you're using - because I'm assuming from the documentation updates that G4 is working just fine for you, even though it won't work for me.
PKPassValidator reports the same thing - here are two near-identical certificates generated from the same code, one using the G1 cert, the other using the G4 cert. PKPassvalidator says the G1 cert is OK, and reports a cert subject mismatch for the G4 cert version:
example-with-G1-WWDC-cert.pkpass.zip example-with-G4-WWDC-cert.pkpass.zip