You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This PR was merged into the 5.4 branch.
Discussion
----------
Use correct tag for ExpoTransportFactory service
| Q | A
| ------------- | ---
| Branch? | 5.4
| Bug fix? | yes
| New feature? | no <!-- please update src/**/CHANGELOG.md files -->
| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->
| Tickets | Fix#44833 <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License | MIT
| Doc PR | -
<!--
Replace this notice by a short README for your feature/bugfix.
This will help reviewers and should be a good start for the documentation.
Additionally (see https://symfony.com/releases):
- Always add tests and ensure they pass.
- Bug fixes must be submitted against the lowest maintained branch where they apply
(lowest branches are regularly merged to upper ones so they get the fixes too.)
- Features and deprecations must be submitted against the latest branch.
- Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
- Never break backward compatibility (see https://symfony.com/bc).
-->
Commits
-------
1d06c4e Use correct tag for ExpoTransportFactory service
angelov
pushed a commit
to angelov/symfony
that referenced
this issue
Jan 11, 2022
Symfony version(s) affected
6.0.0
Description
The expo-notifier transport factory is tagged with
chatter.transport_factory
but must be tagged withtexter.transport_factory
to work properly.symfony/src/Symfony/Bundle/FrameworkBundle/Resources/config/notifier_transports.php
Line 243 in 60ce5a3
How to reproduce
Possible Solution
change
chatter.transport_factory
totexter.transport_factory
insymfony/src/Symfony/Bundle/FrameworkBundle/Resources/config/notifier_transports.php
Line 243 in 60ce5a3
Additional Context
No response
The text was updated successfully, but these errors were encountered: