- How do I send Firebase push notifications through Laravel notifications?
- Add the package's FCM channel to the via() method of a Laravel notification class, define the FCM payload in the notification, and implement routeNotificationForFcm on the notifiable model to return device tokens. The package supports device tokens, topics, conditions, data payloads, and custom sounds. Because the last release is from 2020, verify FCM API compatibility before relying on it.
- How do I install benwilkins/laravel-fcm-notification?
- Install it with Composer in a Laravel application, configure your Firebase Cloud Messaging credentials, and register the FCM channel in the notification class. You also need to implement the notifiable route that supplies FCM device tokens. Treat installation as a proof of concept first because the package has not had a release since October 2020 and may not match current FCM authentication.
- Does benwilkins/laravel-fcm-notification support Laravel 10 or Laravel 11?
- There is no guarantee it supports Laravel 10 or Laravel 11; the last release was October 2020 and likely targets older Laravel and PHP versions. Check Composer constraints against your target matrix and test the exact framework, queue driver, and auth setup. If constraints fail, plan to fork, patch, or replace it.
- Does this package use the FCM legacy API or FCM HTTP v1?
- Given the October 2020 release date, assume the package may use legacy FCM HTTP APIs rather than FCM HTTP v1 with service-account authentication. Legacy FCM APIs have been deprecated and retired, so confirm the implementation before production. If it is legacy-only, budget for a fork or an internal PushSender wrapper around HTTP v1.
- How do I send FCM notifications to topics or conditions with Laravel?
- The package advertises support for device tokens, topics, conditions, data payloads, and custom notification sounds. You configure the target in the notification payload and send through the FCM channel. Topic subscription management and governance remain the host application's responsibility.
- What are alternatives to benwilkins/laravel-fcm-notification for Laravel FCM?
- Consider a maintained Laravel FCM integration, wrapping FCM HTTP v1 behind your own PushSender interface, or forking this package and patching it for current Laravel and FCM HTTP v1. Choose based on your Laravel/PHP matrix, credential model, and whether you need APNs, web push, analytics, or retries. An internal interface isolates the app from package churn.
- Is benwilkins/laravel-fcm-notification maintained?
- It appears lightly maintained, with the last Composer release in October 2020 and no guaranteed security or compatibility updates. Treat it as a tactical adapter and budget internal ownership for dependency review, Laravel upgrades, and FCM API changes. If you adopt it, be prepared to fork and maintain it internally.
- How do I handle invalid device tokens and retries with this Laravel FCM package?
- The package is a narrow notification-channel adapter and does not solve token lifecycle, retries, rate limits, or delivery analytics by itself. Your application should track send attempts, successes, failures, queue lag, and invalid tokens. Run a non-production proof of concept to confirm how invalid tokens and FCM errors surface before production.
- Can I use this package for production push notifications?
- It can be used in production for low-volume, best-effort push if you validate FCM HTTP v1 compatibility, credential handling, queue behavior, invalid-token cleanup, and payload limits. It is not strategic messaging infrastructure and does not provide token lifecycle, analytics, retries, or multi-provider fallback. Roll out behind a feature flag with monitoring, and prefer a maintained HTTP v1 integration or internal wrapper for business-critical delivery.
- How do I test benwilkins/laravel-fcm-notification notifications in Laravel?
- Use Laravel's notification fakes to assert routing and add contract tests around an internal push interface, then run a non-production proof of concept with one notification type and one test device. Mock external FCM calls where possible and verify queue behavior, payload limits, and invalid-token handling. Do not assume 2020-era FCM behavior matches current APIs.