Closed mbabker closed 1 year ago
Uh, that's not good! Thanks for bringing this up! I'll fix and create a release within the next two hours and let you know here. Sorry for the inconvenience!
Lesson learned: Jérôme, don't replace polyfills just because you think an extension is installed because it's included in the require
section.
Release 6.9.2 is out, please let me know if this fixes the problem 🙏
All good, thank you!
This might be a bug in composer itself
Describe the bug
With the introduction of the
replace.symfony/polyfill-mbstring
config in https://github.com/kreait/firebase-php/commit/75857d0b6a4ec2134b8c2c46c3831dec944b7e81, when a project has a dependency that requires thesymfony/polyfill-mbstring
package, the latest versions of this package cannot be installed.In a WIP Laravel project, we've recently installed
laravel-notification-channels/fcm
which indirectly installs this package, and that update installed this package at version 6.8.0. Because of the replace statement, Composer decides it can't update the package.Installed packages
PHP version and extensions
Steps to reproduce the issue.
Error message/Stack trace
Additional information
Removing the
replace
config should fix this issue.