Weave Code
Rms Push Notifications Bundle Laravel Package
opwoco/rms-push-notifications-bundle
A Symfony bundle for integrating RMS push notifications into your application. It provides configuration and delivery support for connecting app events to RMS push services, simplifying notification setup.
Push notifications/messages for mobile devices. Supports iOS, Android (C2DM, GCM), Blackberry and Windows Mobile (toast only). A Symfony2 bundle.
Frequently asked questions about Rms Push Notifications Bundle
- Can I use opwoco/rms-push-notifications-bundle in a Laravel application?
- No. It is a Symfony2 bundle, so Laravel cannot consume its DependencyInjection extension or service-container XML/YAML wiring. You would have to discard the bundle layer and port raw classes into a Laravel service provider and notification channel, which is a rewrite rather than an install.
- Does this package still send iOS and Android push notifications?
- No. Its core transports target the legacy Apple Push Notification Service binary provider and Google Cloud Messaging, both of which vendors shut down. Current APNs requires HTTP/2 with token or certificate auth, and Android requires FCM HTTP v1 with OAuth2 service-account auth. The bundle's central value proposition does not function against production endpoints.
- How do I install opwoco/rms-push-notifications-bundle?
- You can run composer require opwoco/rms-push-notifications-bundle, but installing it does not give you a working Laravel integration. The package expects Symfony2 bundle registration and container configuration, not Laravel's package discovery or config publishing. For a modern Laravel app, do not install it; choose a maintained push provider instead.
- Which Laravel versions support this package?
- None. There is no Laravel service provider, facade, or Notification channel in the package, and it is built around Symfony2 idioms. No Laravel version can use it as intended without a port.
- Is this package maintained and safe for production?
- It has zero stars and zero dependents, no upstream activity, and no issue history or security patch stream. The transports are retired, so the practical risk is not just instability but unusability. Do not put it into production; the MIT license permits a fork but creates no support obligation.
- What should I use instead for push notifications in Laravel?
- Use Laravel's Notification facade with custom channels that call FCM HTTP v1 for Android and APNs HTTP/2 with token-based JWT auth for iOS. Dispatch delivery through queued jobs so retries and observability use your existing queue infrastructure. Below roughly 10k notifications per day, a managed service such as Firebase, OneSignal, or Pusher Beams is often cheaper than building and operating your own transports.
- Can I fork this bundle and update the dead transports?
- You can fork it under the MIT license, but updating the transports is a rewrite, not a patch. You would need to implement APNs HTTP/2 with a .p8 key and FCM HTTP v1 with OAuth2 service-account auth, then re-host any useful logic as a Laravel service provider and channel. The original can serve as reference material, but the cost usually exceeds adopting a maintained alternative.
- What configuration does the bundle require?
- It uses Symfony2 service-container XML/YAML and a DependencyInjection extension to wire RMS push services into a Symfony application. It does not provide Laravel config files, package discovery, or a Notification channel. That configuration model is not directly usable in Laravel.
- Will this package run on PHP 8?
- A Symfony2-era codebase is unlikely to run cleanly on PHP 8.x because of dependency and event-dispatcher changes; Symfony moved its base Event class to the Contracts EventDispatcher component in 4.3. Even if some classes load, the APNs and GCM transports are dead. Treat PHP 8 support as unsupported unless you port the code.
- How should I test push notifications if I inherit a legacy integration?
- First determine whether the legacy system currently sends push successfully and through which endpoint, because that reveals whether a hidden patched transport exists. Build integration tests around the actual live provider, whether FCM HTTP v1 or APNs HTTP/2, and verify device-token lifecycle handling and credential rotation. Do not assume this bundle works; log delivery results from test devices before planning any migration.
Weaver
How can I help you explore Laravel packages today?