Web Push Notifications are broken in Chrome/PWA app on Android >=13 Work Profile [296891218]

Infeasible

Bug

[AOSP] assigned

Status Update

No update yet.

Description

wo...@mateco.eu

created issue #1

Aug 22, 2023 09:09AM

Since Android 13, Web Push Notifications are broken for Progressive Web Apps executed via Chrome or via the "standalone PWA app" in the Work Profile of Android Enterprise devices.

We reported this issue before on

https://issuetracker.google.com/issues/277852487 , including test data for Android 13 and 14, but that report was for some unknown reason marked as "Won't fix".

In the meantime, Samsung Knox also published the issue on their website:

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/kbas/kba-360043326193/ . We cannot apply their proposed fix as we rely on fully-managed Android devices, without Personal Profile.

As we, just like many other websites, strongly rely on Web Push Notifications to provide our users with important information asap, we are significantly impacted by this issue. We also found other reports of "broken notifications" on community forums that may be related, e.g., by GMail users on

https://eu.community.samsung.com/t5/galaxy-s21-series/work-profile-gmail-not-working/td-p/6437094 .

Thanks in advance for having another look at this issue, we're still eagerly waiting for a fix!

Comments

wo...@mateco.eu <wo...@mateco.eu> #2Aug 22, 2023 09:32AM

It looks like you are raising an issue as an Android user, rather than an Android Open Source Developer.

For user support, please see the Android Help Center or post on our Android Help Community.

For Pixel phone support, please see the Pixel Help Center or post on our Pixel Help Community.

Support for other devices is provided by the device manufacturers or by the carriers selling those devices, see here to get manufacturer help for your Android device.

su...@google.com <su...@google.com> #3Aug 22, 2023 06:31PM

Assigned to su...@google.com.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

ra...@google.com <ra...@google.com> Sep 1, 2023 05:56AM

Reassigned to vi...@google.com.

31...@gmail.com <31...@gmail.com> #4Nov 16, 2023 02:13PM

Any updates? Need fix soon!

vi...@google.com <vi...@google.com> #5Nov 16, 2023 07:32PM

Status: Won't Fix (Infeasible)

This forum is for reporting android issues only, However the issue you have logged is related to Chrome. Please report this kind of issues to Chrome developers in the below link, https://bugs.chromium.org/p/chromium/issues/list.

However, we have filed the bug on your behalf, please track track the status of the bug in the below given link: https://bugs.chromium.org/p/chromium/issues/detail?id=1502891.

wo...@mateco.eu <wo...@mateco.eu> #6Nov 17, 2023 06:41AM

Thanks for the detailed status update.
While submitting this report, I also reported it on chromium; see

https://bugs.chromium.org/p/chromium/issues/detail?id=1474808 . This report is now duplicating your report (

https://bugs.chromium.org/p/chromium/issues/detail?id=150289).

Sadly, no news so far.

wo...@mateco.eu <wo...@mateco.eu> #7Nov 17, 2023 06:54AM

PS: since the issue started with Android 13, it's difficult to understand that this is a pure Chrome issue.
Unless Chrome also did a major upgrade coupled to Android 13?