Saturday, November 8, 2025
2 changes · saas-18.2
Resolved issues and error corrections
This fixes an error that could appear when a user manually removed the browser background worker used for Odoo push notifications. Odoo now waits until the browser has fully reactivated that worker before reconnecting notifications, reducing confusing failure messages after a refresh.
Original PR description
When you manually unregister the ServiceWorker linked to your Odoo,
you may receive a notification "Failed to enable push notifications".
This occurs because the ServiceWorker associated with the previous
subscription is gone and the browser has lost the link between the
subscription and the Odoo instance.
To handle this case, we ensure waiting the activated state of the
registration of the service worker before subscribing to the web push
notification.
Steps to reproduce:
- In Odoo, enable push notifications.
- Inside another tab, go to the internal Chrome URL:
chrome://serviceworker-internals/?devtools
- Unsubscribe the ServiceWorker linked to your Odoo instance.
- In the Odoo instance tab, press F5.
=> You will see an internal notification stating
"Failed to enable push notifications" => BUG.
Forward-Port-Of: odoo/odoo#235005
Forward-Port-Of: odoo/odoo#234930This fix keeps Odoo's email server tests and certificate handling working correctly on newer Debian Trixie environments. It updates how local addresses and secure certificate objects are handled, reducing warnings and environment-specific failures.
Original PR description
Forward-Port-Of: odoo/odoo#233914 Forward-Port-Of: odoo/odoo#232699