Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip some more notification data items if they are blank #5041

Merged

Conversation

jpelgrom
Copy link
Member

@jpelgrom jpelgrom commented Feb 10, 2025

Summary

Fixes #5038

Previously FCM would omit blank keys. This was changed and is now in line with websocket notifications, but in some places the behavior might be unexpected. This PR ignores a couple more keys if blank (like we already do for many) where it seems safe to do so.

Screenshots

n/a

Link to pull request in Documentation repository

n/a

Any other notes

Testing note: if you try to send nothing from dev tools it will send a string null, so send a blank string "" instead

@dshokouhi dshokouhi enabled auto-merge (squash) February 10, 2025 18:49
@dshokouhi dshokouhi merged commit 5a3a64d into home-assistant:master Feb 10, 2025
4 checks passed
@jpelgrom jpelgrom deleted the skip-some-blank-notification-data branch February 10, 2025 18:51
@SgtBatten
Copy link

Thanks so much.

I'm not overly familiar with the update cycle of the app. Will this appear in the change notes of a future update?

@jpelgrom
Copy link
Member Author

jpelgrom commented Feb 10, 2025

No, bugfixes will generally not be called out in release notes.

We did mark another beta for release after merging this so it should be available within a day or two from Google Play (version 2025.2.3 of the app).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blank subject key causes message key to not be displayed.
3 participants