- How do I install davibennun/laravel-push-notification in a Laravel app?
- Install it with Composer using composer require davibennun/laravel-push-notification, then register the service provider and facade alias in config/app.php on legacy Laravel 4 or 5 projects. Modern Laravel versions are unlikely to resolve compatible Illuminate constraints. Pin the exact package version and validate the Composer dependency graph before adding it to an existing application.
- Which Laravel and PHP versions does this package support?
- The package targets legacy Laravel 4 and Laravel 5 stacks and depends on old Illuminate versions. It is not designed for modern Laravel or PHP 8+ applications. Check the original composer.json constraints and test against your actual PHP, OpenSSL, and Laravel versions before relying on it.
- Does davibennun/laravel-push-notification still work with GCM for Android?
- The Android path historically used GCM, which Google shut down and replaced with FCM. That means GCM-based delivery is effectively non-viable today without changing the transport. Treat the Android side as broken and migrate to FCM HTTP v1 behind an internal adapter.
- How do I send a push notification to multiple devices with this package?
- The package provides a unified API for dispatching notifications to one or many device tokens, but the underlying sends are likely per-device with limited batching. For large volumes, wrap calls behind a queue job and your own PushGateway interface. Avoid scattering facade calls throughout domain code so you can replace the transport later.
- Can I use davibennun/laravel-push-notification with Laravel queues?
- The package integrates with Laravel's config, queue, and service container, so you can dispatch sends from queued jobs in a legacy application. However, retry semantics, dead-token handling, and delivery observability are not adequately addressed for modern production expectations. Add your own retry, logging, and token cleanup around it.
- How do I configure APNs certificates and GCM credentials for this package?
- Configuration typically involves publishing or editing the package config with an APNs certificate path and passphrase plus a GCM API key. The iOS path relies on older certificate-based APNs flows, so certificate rotation and lifecycle management are your responsibility. Store credentials securely and document ownership before using it in production.
- Is davibennun/laravel-push-notification maintained?
- No, the repository is archived, so there are no upstream security patches, framework compatibility updates, or provider modernization. The 1,225 GitHub stars reflect historical adoption, not current maintainability. Your team must own any fork, dependency security, and provider API changes.
- What are good alternatives to davibennun/laravel-push-notification?
- For modern Laravel, prefer maintained notification channels or direct FCM HTTP v1 and APNs HTTP/2 token-based integrations. You can wrap either transport behind an internal PushGateway interface. This keeps domain code independent of any single package and simplifies future replacement.
- How do I migrate from davibennun/laravel-push-notification to FCM and APNs?
- First inventory all package usage, credentials, and delivery paths, then isolate legacy calls behind an internal PushGateway interface. Migrate Android off GCM to FCM first because GCM is already broken, then move iOS to token-based APNs. Run pilots behind feature flags, compare delivery metrics, and remove the package only after rollback is proven.
- What are the production risks of using this package?
- The main risks are high: archived maintenance, GCM shutdown, legacy APNs certificate flows, missing retry and dead-token handling, and weak observability. It fits only as a short-term bridge inside an isolated legacy adapter. Budget for a fork or replacement and define an exit timeline and acceptable risk window.