- Is eo/passbook-bundle a Laravel package?
- No. It is a Symfony 2.1+ bundle that registers through AppKernel::registerBundles() and relies on Symfony's DI container and FrameworkBundle conventions. There is no Laravel service provider, publishable config, or facade, so it will not drop into a Laravel application in any supported way.
- Can I use EoPassbookBundle in a Laravel application?
- Not directly. The bundle is a thin dependency-injection wrapper around eymengunay/php-passbook, so any Laravel integration has to happen at that library layer or through your own port. The practical path is requiring php-passbook directly, then writing a Laravel service provider and a swappable WalletPassGenerator interface instead of trying to boot the Symfony bundle inside Laravel.
- What Laravel version does eo/passbook-bundle support?
- None. The package targets Symfony 2.1+ and has no Laravel support matrix at all. Its Symfony 2.1-era Composer constraints are likely to conflict with modern Laravel and PHP 8.x dependencies, so expect resolver failures rather than a clean install.
- How do I install eo/passbook-bundle with Composer?
- On Symfony you require eo/passbook-bundle at dev-master, enable Eo\PassbookBundle\EoPassbookBundle in AppKernel, and add the eo_passbook configuration block to config.yml. Those steps do not map to Laravel, where you would instead evaluate the underlying php-passbook library and wire it up yourself.
- What certificates do I need to generate .pkpass files?
- You need a Pass Type ID .p12 certificate with its password plus Apple's WWDR intermediate certificate. The bundle also requires pass type identifier, team identifier, organization name, output path, and an icon file, and all configuration values are mandatory. Verify your WWDR intermediate against Apple's current chain, because older generations expired in 2023.
- Does eo/passbook-bundle support Apple Wallet pass updates via APNs?
- The bundle documentation covers pass generation only, not the PassKit Web Service endpoints or push update flow. Apple retired the legacy binary APNs provider protocol in favor of HTTP/2, so confirm what the underlying php-passbook library actually implements before planning live updates. If updates are on your roadmap, budget for implementing the web service and HTTP/2 push yourself.
- Is eo/passbook-bundle still maintained?
- No. The repository has had no releases since January 2018, with roughly 10 stars, zero dependents, and a single maintainer. There is no security response or compatibility patching, so treat it as a reference implementation of the signing pipeline rather than a production dependency.
- What is the best alternative for Apple Wallet passes in Laravel?
- The functional code lives in eymengunay/php-passbook, so wrapping that library behind your own interface is the lowest-effort route. You can also evaluate a maintained package that handles pass.json assembly, manifest hashing, and PKCS#7 signing. Avoid depending on the Symfony bundle directly, since none of its integration layer transfers to Laravel.
- How do I configure the pass type and team identifiers?
- In Symfony you set pass_type_identifier, team_identifier, and organization_name under eo_passbook in config.yml. These values must match the identifiers registered in your Apple Developer account for the Pass Type ID used to sign the pass. In Laravel you would move the same values into a config file that feeds your own generator.
- How can I test .pkpass generation before shipping?
- You can inspect the generated bundle locally: pass.json, assets, manifest.json with SHA-1 hashes, and a detached PKCS#7 signature. Installing on a device requires Apple Wallet, a valid Pass Type ID, and a current WWDR chain. Because certificate failures are silent server-side, add explicit signature verification and alerting rather than relying on manual spot checks.