starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Google Workspace/Chat not showing notification content on android due to buggy impl on googles side #4082

New issue

Open

opened 2026-02-28 03:50:35 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 03:50:35 -05:00

Owner

Originally created by @Mazvy on GitHub (Apr 15, 2025).

My previous report: https://github.com/louislam/uptime-kuma/issues/5569
2.0.0-beta.2 PR: https://github.com/louislam/uptime-kuma/pull/5476

🏷️ Feature Request Type

Change to existing monitor

🔖 Feature description

The notification is now in a way even worse on Android.
It just shows an empty notification.

On Windows (Chrome!) it's the same story.

I don't understand what was changed as it not only hasn't solved this issue, but somehow made it even worse as they're now just entirely empty notifications with only the title popping up.

✔️ Solution

Please revert to plaintext notification contents.

The cardv2 message in Google Chat looks great, but personally I believe that it's more important to have a notification that is instantly readable. Sticking to cardsv2 while waiting for Google to fix a 2+ year old bug is not a solution.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Mazvy on GitHub (Apr 15, 2025). ### 📑 I have found these related issues/pull requests My previous report: https://github.com/louislam/uptime-kuma/issues/5569 2.0.0-beta.2 PR: https://github.com/louislam/uptime-kuma/pull/5476 ### 🏷️ Feature Request Type Change to existing monitor ### 🔖 Feature description The notification is now in a way even worse on Android. It just shows an empty notification. ![Image](https://github.com/user-attachments/assets/32a93fd0-1a14-4b45-8e95-57c7683afe3c) On Windows (Chrome!) it's the same story. ![Image](https://github.com/user-attachments/assets/98dcfc2c-2d21-4a37-a6e7-7c6ce25c8f2f) I don't understand what was changed as it not only hasn't solved this issue, but somehow made it even worse as they're now just entirely empty notifications with only the title popping up. ![Image](https://github.com/user-attachments/assets/4e95ef88-41d1-401b-a68a-52d0044dcf54) ### ✔️ Solution Please revert to plaintext notification contents. The cardv2 message in Google Chat looks great, but personally I believe that it's more important to have a notification that is instantly readable. Sticking to cardsv2 while waiting for Google to fix a 2+ year old bug is not a solution. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:notifications

blocked-upstream

labels

2026-02-28 03:50:35 -05:00

deekerman commented

2026-02-28 03:50:38 -05:00

Author

Owner

@Mazvy commented on GitHub (Jul 25, 2025):

I would like to propose removing the blocked-upstream tag, as this is a "self block" by refusing to revert to using plain text message contents and instead insisting on waiting for Google to fix their cardv2 implementation which they haven't properly even acknowledged.

Before the beta - event information was available in the notification as it should be. There is already code for that, just revert OR add an option Google Workspace (Legacy) for those who value seeing alert messages properly.

@Mazvy commented on GitHub (Jul 25, 2025): I would like to propose removing the `blocked-upstream` tag, as this is a "self block" by refusing to revert to using plain text message contents and instead insisting on waiting for Google to fix their cardv2 implementation which they haven't properly even acknowledged. Before the beta - event information was available in the notification as it should be. There is already code for that, just revert OR add an option `Google Workspace (Legacy)` for those who value seeing alert messages properly.

deekerman commented

2026-02-28 03:50:41 -05:00

Author

Owner

@Erikel746 commented on GitHub (Aug 6, 2025):

I can do a PR with a new notification provider Google Workspace (Legacy) if thats wanted. I dont think google will fix the bug with cards v2 in the near future. This is not fixed after 2 years in the Google Issue Tracker.

@Erikel746 commented on GitHub (Aug 6, 2025): I can do a PR with a new notification provider Google Workspace (Legacy) if thats wanted. I dont think google will fix the bug with cards v2 in the near future. This is not fixed after 2 years in the Google Issue Tracker.

deekerman commented

2026-02-28 03:50:41 -05:00

Author

Owner

@Mazvy commented on GitHub (Aug 7, 2025):

I can do a PR with a new notification provider Google Workspace (Legacy) if thats wanted. I dont think google will fix the bug with cards v2 in the near future. This is not fixed after 2 years in the Google Issue Tracker.

Yes, please! Kuma is such a great tool, but seeing this for important "notifications" is just .... not good.
I'd much rather have the plaintext version than this:

@Mazvy commented on GitHub (Aug 7, 2025): > I can do a PR with a new notification provider Google Workspace (Legacy) if thats wanted. I dont think google will fix the bug with cards v2 in the near future. This is not fixed after 2 years in the Google Issue Tracker. Yes, please! Kuma is such a great tool, but seeing this for important "_notifications_" is just .... not good. I'd much rather have the plaintext version than this: <img width="490" height="177" alt="Image" src="https://github.com/user-attachments/assets/1dafe739-c4f2-46eb-b70b-c257c564fb87" /> <img width="1080" height="650" alt="Image" src="https://github.com/user-attachments/assets/3521e40f-b5c0-4a0f-b137-dbe15f47d9e2" />