November 2013
Intermediate to advanced
576 pages
19h 3m
English
Passbook requires passes be cryptographically signed to ensure that a pass was built by the provider and has not been modified in any way. To sign a pass, a Pass Type ID needs to be established in the iOS Provisioning Portal and a pass signing certificate specific to the Pass Type ID needs to be generated. After the Pass Type ID and certificate are available, passes can be signed. For each unique pass instance a manifest file with checksums for each file in the pass needs to be built so that Passbook can verify each file.
Read now
Unlock full access