Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Rms Push Notifications Bundle

Rms Push Notifications Bundle Laravel Package

inscouts/rms-push-notifications-bundle

A Symfony bundle that integrates RMS push notifications into your PHP application, providing services and configuration to send notifications through the RMS platform with minimal setup in your Symfony project.

View on GitHub
Deep Wiki
Context7

Fork of richsage/RMSPushNotificationsBundle.

Frequently asked questions about Rms Push Notifications Bundle
Is inscouts/rms-push-notifications-bundle a Laravel package?
No. It is a Symfony 2 bundle that registers through a Bundle class, a DependencyInjection extension, and Symfony container service definitions. Laravel's package discovery and service container have no mechanism to register or boot it, so a simple composer require will not produce a working integration.
Can I install this RMS push bundle in Laravel 10 or 11?
Not practically. The bundle targets Symfony 2-era components and PHP constraints that conflict with Laravel 10 and 11, which require PHP 8.1 or newer. Composer resolution will likely fail or force downgrades across your application. Making it run would mean booting a partial Symfony kernel inside Laravel or hand-porting the transport classes.
Does this package still work with Apple APNs?
No. Its APNs transport uses Apple's legacy binary provider protocol, which Apple shut down in March 2021. Modern APNs requires HTTP/2 with token-based JWT or certificate authentication. This bundle cannot deliver notifications to current APNs endpoints.
Does this bundle support GCM or FCM for Android push notifications?
It targets GCM and C2DM, which Google deprecated and shut down in 2019 in favor of FCM HTTP v1. There is no FCM HTTP v1 support in this bundle. For Android today you need a maintained FCM library or a hosted service.
How do I install and configure this bundle in a Symfony project?
Installation is via Composer, followed by registering the bundle in your Symfony kernel and configuring its DependencyInjection extension tree. However, this is a fork of an abandoned upstream with zero stars and no dependents, and its transport protocols are discontinued. Even on Symfony, treat it as reference code rather than a runtime dependency.
What Laravel package should I use for iOS APNs push notifications?
Use a maintained HTTP/2 token-auth transport such as edamov/pushok or laravel-notification-channels/apn. Both support modern APNs authentication and integrate with Laravel's notification system. Avoid certificate-rotation-heavy legacy implementations like this bundle.
What are the best Laravel alternatives for FCM push notifications?
For Firebase Cloud Messaging HTTP v1, kreait/laravel-firebase and laravel-notification-channels/fcm are common choices. They support service-account authentication and current FCM endpoints. Laravel's native Notification system lets you wire either one as a custom channel.
Is this package maintained and safe for production?
No. It is a fork of richsage/RMSPushNotificationsBundle, which is abandoned, and the fork has zero stars, zero dependents, and a single owner. The Symfony 2-era code has not been audited against modern CVEs, and its transitive dependencies are likely pinned to old versions with known issues. Production use carries high abandonment, security, and runtime risk.
Can I use this bundle as a reference for push payload construction and device token handling?
Yes, that is its most realistic value. The transport classes show how push payloads and device tokens were structured for APNs, GCM, and BlackBerry BIS. Copy those ideas into your own PushTransport contract instead of depending on the package.
How do I migrate from this RMS push bundle to a Laravel push notification setup?
First inventory your device platforms, token stores, and delivery SLAs. Define a PushTransport contract in your Laravel app with send, validate-token, and receipt methods so the vendor choice stays swappable. Then implement APNs HTTP/2 and FCM HTTP v1 using maintained libraries, and quarantine the legacy bundle behind that interface if it still runs somewhere.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
abbasudo/artisan-route
mirvan/ippanel
ignibyte/aic-framework
glavweb/data-schema-bundle
glavweb/datagrid-bundle
tacticmedia/scim-server
uni-method/frame
neika-ai/sdk
adachsoft/php-code-style
pharaonic/laravel-notification-dependencies
beautinow/translug
dev-brainiac/bot-cloaked
octoberrain/html
octoberrain/extension
octoberrain/exception
octoberrain/contracts
adachsoft/api-version-bundle
cgv/localized-resource
noith/settings
kda/laravel-package