启用推送通知时，如果需要同意，则不会实际订阅

justinm · 2025 年8 月 31 日 02:36

app/assets/javascripts/discourse/app/services/desktop-notifications.js

bb6c5c9fa


      
          @action
          async enable() {
            if (this.isPushNotificationsPreferred) {
              await subscribePushNotification(() => {
                this.setIsEnabledPush(true);
              }, this.siteSettings.vapid_public_key_bytes);
          
              return true;
            } else {
              await Notification.requestPermission((permission) => {
                confirmNotification(this.siteSettings);
                if (permission === "granted") {
                  this.setIsEnabledBrowser(true);
                  return true;
                } else {
                  return false;
                }
              });
            }
          }

在初始引导过程中，我注意到 iOS 用户会将论坛安装为 PWA，然后在首次打开 PWA 时收到通知同意横幅。
如果他们在该同意横幅中点击“启用通知”，系统会提示他们授予权限，之后会向他们发送确认通知。

然而，这实际上并没有订阅用户的推送通知，这是出乎意料的！

看起来对于通知同意横幅，这里的代码会首先进入 else 路径以请求用户同意（Notification.requestPermission），但它将_不会_订阅推送通知（subscribePushNotification）。

此时的解决方法是让用户前往他们的通知偏好设置并点击那里的“启用通知”按钮。

justinm · 2025 年8 月 31 日 03:02

github.com/discourse/discourse

UX: Improve robustness of notification logic

main ← DrChat:pushnotifs

opened 03:01AM - 31 Aug 25 UTC

DrChat

+276 -140

https://meta.discourse.org/t/enabling-push-notifications-does-not-actually-subsc…ribe-if-consent-is-required/381043 Discourse currently supports two different types of notifications: * Desktop (browser) notifications: these are used on desktop when the user has a Discourse tab open but idle. * Push notifications: these are used both for desktop and mobile to notify a user about activity when they may not have any Discourse tabs open. There is some amount of conflation of these two distinct types, and on iOS I've observed that users can enable the former notifications but not the latter (and the former is useless on mobile). There should be a stronger distinction between the two types, and mobile devices should _never_ go down the former path since they will typically never have Discourse open in the background! --- This pull request does the following: * App startup is deferred until the service worker is installed (previously: this was done asynchronously). The registration is now available in a global. * The notification consent banner is now displayed when the device supports notifications (previously: only in PWA). This change will be **widely visible to all users of Discourse**. * The dismissal state for the notification consent banner has been reset for all users. * If push notifications are preferred, we no longer implicitly fall back to desktop notifications and they are _implicitly disabled if already enabled_. * Added a new getter to the notification consent banner that can be used to determine if a PWA is needed (`isPushPwaNeeded()`)

sam · 2025 年8 月 31 日 23:27

非常感谢您在此处提供的详细拉取请求，团队将在未来几周内进行审查！

justinm · 2025 年9 月 1 日 22:30

谢谢！

自从发布以来，我在这项拉取请求（PR）上做了更多工作——希望不会太麻烦
我认为这将大大改善 Discourse 与 WebPush 的集成，并且应该为您提供一个扩展点，您可以使用它来促使 iOS 用户安装 Discourse 作为 PWA。

justinm · 2025 年9 月 4 日 19:40

我已经将该更改部署到我的论坛，并且现已上线。
我认为这将真正增加用户的参与度

我已经请人检查了我的论坛，并确认他们被要求启用推送通知（在桌面和 Android 上）。他们也已在后端注册（在 push_notifications 表中）。
现在只剩下让其他人再次检查论坛了。

附注：此提示仍然受此设置的限制：

sam · 2025 年9 月 15 日 01:59

感谢这里所做的所有工作，我们现在刚从会议回来，我们将在未来几周内对其进行正式审查。

话题		回复	浏览量
Push notifications PWA or iOS Feature pwa , push-notifications	6	121	2025 年7 月 14 日
Feature request: Teach iOS users to A2HS/Push Feature	16	1834	2023 年6 月 1 日
Discourse PWA notifications Support	3	906	2021 年8 月 6 日
Push Notifications on iOS Support	10	2949	2020 年2 月 19 日
Push Notifications Not functioning Support	23	3271	2019 年6 月 2 日

启用推送通知时，如果需要同意，则不会实际订阅

相关话题