- Is mcfedr/awspushbundle compatible with Laravel?
- No. mcfedr/awspushbundle is a Symfony bundle that ships a Bundle subclass, a DI Extension with a Configuration tree, and compiler passes, none of which Laravel can bootstrap. Composer will autoload its classes, but you get no service provider, config publishing, or container wiring. Only the underlying plain-PHP SNS wrapper classes are realistically reusable in a Laravel app.
- Can I install mcfedr/awspushbundle in a Laravel project with Composer?
- You can require it, but installation alone gives you autoloaded classes and nothing else. Laravel has no equivalent path for the Symfony bundle bootstrapping, so the bundle's services and console commands will not be registered. Treat it as a library only if you are prepared to instantiate its manager classes yourself from a Laravel service provider.
- How do I use Amazon SNS push notifications in Laravel with this package?
- The practical approach is to skip the bundle and wrap Aws\Sns\SnsClient directly in a small PushGateway interface bound in a Laravel service provider. The bundle's own classes are thin glue over methods like createPlatformEndpoint, subscribe, and publish, and they are not written against Laravel contracts such as queues, events, or logging. Reimplementing that wrapper in-house is roughly a two-to-four day task and removes the Symfony dependency risk.
- Does mcfedr/awspushbundle support APNS token-based auth with a .p8 key?
- The provided evaluation does not confirm this; it is listed as an open question to verify in the bundle's Configuration tree before committing. Certificate-based APNS auth is the traditional SNS path, and certificate rotation is a recurring ops burden. Check whether the configuration surface accepts a .p8 key and key ID, or only certificate paths.
- Is the FCM path in mcfedr/awspushbundle aligned with FCM v1?
- Because delivery is delegated to Amazon SNS, FCM v1 semantics should be inherited from the AWS platform rather than implemented by the bundle. The evaluation still recommends confirming that the platform-application creation path is not pinned to legacy FCM HTTP API behavior. The legacy FCM API is retired, so this matters for Android delivery.
- What are the limitations of using Amazon SNS for mobile push?
- SNS imposes a 256 KB payload ceiling, no rich media, no per-message delivery receipts beyond CloudWatch aggregates, no scheduling, and no templating beyond simple attribute substitution. It also lacks PublishBatch support for direct-to-endpoint mobile push. Those constraints apply whether you use this bundle, a fork, or your own wrapper, because they live in SNS rather than the package.
- How does mcfedr/awspushbundle handle device tokens and endpoint cleanup?
- The bundle provides helpers for managing device endpoints and tokens, but the evaluation flags EndpointDisabled handling and token-pruning hooks as unconfirmed. Invalid-token cleanup may fall entirely on your application. Plan to subscribe to SNS delivery feedback or reconcile endpoints yourself rather than assuming the bundle prunes stale tokens.
- Is mcfedr/awspushbundle actively maintained and safe for production?
- It is MIT licensed and had a release in February 2025, so it shows signs of maintenance. The risks are a single maintainer, roughly 40 GitHub stars, and zero dependents, meaning little battle-testing and no Stack Overflow corpus. For a Laravel production app, the architectural mismatch is a bigger concern than code quality given the small code volume.
- What Symfony version does mcfedr/awspushbundle require, and will it conflict with Laravel?
- The evaluation lists this as a key compatibility question: Laravel 11 typically pins Symfony 7 components, while Laravel 10 uses Symfony 6.2. If the bundle's symfony/* constraints conflict with your Laravel version's pinned components, the consume-as-a-library path is dead. Check composer constraints before assuming you can require it alongside a Laravel app.
- What is the best alternative to mcfedr/awspushbundle for Laravel push notifications?
- For Laravel, the cleanest option is a thin in-house PushGateway built directly on aws/aws-sdk-php, with methods like registerDevice, unregisterDevice, sendToDevice, and sendToTopic. That keeps SNS domain knowledge in your codebase and avoids a Symfony bundle you cannot debug through Laravel's container. If you do not need SNS specifically, evaluate Laravel-native notification channels or a dedicated push service instead.