Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[Notifier] Firebase error handling#42690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:5.3frommishaklomp:firebase-error-handling
Aug 23, 2021

Conversation

@mishaklomp
Copy link
Contributor

QA
Branch?5.3
Bug fix?yes
New feature?no
Deprecations?no
TicketsFix#42211
LicenseMIT
Doc PRsymfony/symfony-docs

I found a bug in the Firebase error handling, resulting in aUndefined index: message_id error.
It occurred when trying to send a notification to an unregistered device token. As I stated in my issue before.

Don't know if this (little) change should include any tests?
This is my first PR, so any feedback is welcome!

so the transports doesn't try setting the success message, that doesn't exists.
@carsonbot
Copy link

Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has acontribution guide which I suggest you to read.

In short:

  • Always add tests
  • Keep backward compatibility (seehttps://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (seehttps://symfony.com/releases)
  • Features and deprecations must be submitted against the 5.4 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

@fabpot
Copy link
Member

Thank you@mishaklomp.

mishaklomp reacted with laugh emoji

@fabpotfabpot merged commit8a33e05 intosymfony:5.3Aug 23, 2021
@fabpotfabpot mentioned this pull requestAug 30, 2021
fabpot added a commit that referenced this pull requestOct 12, 2021
…sport (villfa)This PR was merged into the 5.3 branch.Discussion----------[Notifier] Fix 'Undefined array key' error in FirebaseTransport| Q             | A| ------------- | ---| Branch?       | 5.3| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       |Fix#42841| License       | MIT| Doc PR        | n/aThis modification fixes a remaining `Undefined array key` error in *FirebaseTransport*.It also add a test to cover#42690.<!--Replace this notice by a short README for your feature/bugfix. This will help peopleunderstand your PR and can be used as a start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Never break backward compatibility (seehttps://symfony.com/bc). - 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 branch 5.x. - Changelog entry should followhttps://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry-->Commits-------53f836e [Notifier] Fix 'Undefined array key' error in FirebaseTransport
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

@OskarStarkOskarStarkOskarStark approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

5.3

Development

Successfully merging this pull request may close these issues.

4 participants

@mishaklomp@carsonbot@fabpot@OskarStark

[8]ページ先頭

©2009-2025 Movatter.jp