Is there something wrong with my Personalization File?

Question

Created Jul ’20

Replies 1

Boosts 0

Participants 2

Is this correct?

{
"requiredPersonalizationFields" : [
"PKPassPersonalizationFieldName",
"PKPassPersonalizationFieldPhoneNumber"
],
"description": "This is a test description.",
"termsAndConditions" : "These are test terms and conditions."
}

When I include it in my Pass Bundle (personalization.json) the pass wont open. When I remove it, it does.

Very weird as I copied and pasted structure from Apple Docs.

I have also checked that the SHA1 Hash (seen in manifest) matches the file. Which it does.

Has anyone successfully used a personalization.json file before?

Ref

https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/PassKit_PG/PassPersonalization.html

If it's correct, are the other things I need to check or have in place to generate the PKPASS file featuring the Personalization Questionaire?

Thanks

Boost

Answer 1

paracelsus OP

Jul ’20

I'm also interested in an official response to this question. First, my assumptions:

the personalization.json file, and any logo images, are hashed as normal and included in the manifest file
the pass needs to support NFC entries in the dictionary
to include NFC entries, you need to get an "enhanced certificate" by submitting an application form to Apple.

So, without knowing for sure, I'm guessing our "personalizable" pass is not validating because w don't have NFC entries and we don't have an NFC certificate.

I have a workaround for effectively completing the personalization process, but I would rather have access to NFC tags.

I also suspect that part of the reason we don't hear more about this, is because App Clips will soon support the new NFC tags announced at WWDC 2020, and that support for personalizable, NFC-aware wallet passes is not as emphasized as we'd like.

0