4.1.0

A collection of Kreait\Firebase\Messaging\MulticastSendReport is now returned from the channels send method, making the response available in the Illuminate\Notifications\Events\NotificationSent event.

4.0.0

This new major version includes breaking changes. We remove support for older versions of Laravel and PHP, adopt new PHP syntax, clean up a lot of boilerplate and improve test coverage. Support for using custom Firebase connections on-demand has also been greatly improved giving more control where required.

Please review the CHANGELOG and docs for changes, specifically related to:

• Building an FcmMessage object (new arguments and less resource classes), and
• Handling notification failures (you will now receive the underlying report to handle as you need).

3.2.1

• Removed some built assets from the library
• Made a GitHub release for clarity

2.5.0

What's Changed

• Fix for "A message can only have one of the following targets" error by @mgsmus in #116
• Add more specific parameter type for setData() method by @maximal in #114

New Contributors

• @mgsmus made their first contribution in #116
• @maximal made their first contribution in #114

Full Changelog: 2.4.0...2.5.0

2.4.0

What's Changed

• Support for version 4.0 of laravel-firebase by @dododedodonl in #98

Full Changelog: 2.3.1...2.4.0

2.3.1

What's Changed

• chore: style fixes by @atymic in #101
• fix: mixed return type by @atymic in #106

Full Changelog: 2.3.0...2.3.1

2.3.0

What's Changed

• Add support for Laravel 9.x by @marcroberts in #100

New Contributors

• @marcroberts made their first contribution in #100

Full Changelog: 2.2.1...2.3.0

2.2.1: Fix Catch Exception when resolving FirebaseManager (#73)

My Case is the Following:

- I'm working with laravel v5.8 (a Legacy project and can't upgrade it now).

- I installed this package with version v2.2

- The Package using `laravel-firebase` with version v2.4 which support laravel v5.8

My Problem:
- Because `laravel-firebase`  v2.4 installed this version didn't bind `firebase.manager` in laravel service container
- This means it should fallback and enter the catch block and use `firebase.messaging`.
- But the problem is the catch block trying catch `BindingResolutionException` but in my case, the exception was `ReflectionException`.
- I don't know what is the problem maybe because I'm working with the old laravel version but I hope you find this solution helpful.

Laravel firebase 3 support

Add support for laravel-firebase 3.0 (#65)

Co-authored-by: Tom Janssen <[email protected]>

2.1.3

Partially Revert #64 to fix #69 (#70)