IPS Push Notifications Bug in Firefox

[Mote Marketing, Inc.]

My Developers confirm that this is an IPS bug (probably specific to the latest update (v4.6.10):

• Browser: Firefox v97.0 (64-bit). Does not appear to affect the latest versions of Microsoft Edge or Google Chrome browsers.
• OS: Windows 11 Home, v10.0.22000 (64-bit)
• Description: The push notifications popup thrown by IPS enters an endless loop when the user attempts to enable push notifications in Firefox ("Enabling..." just keeps churning forever (see attached image).

[Jim M]

Are there any errors in the browser console when this is encountered? 

 

If you go to {your-base-url}/notifications/options/ are push notifications enabled? (note: you'll want to replace {your-base-url} with the base url of your community)

[Mote Marketing, Inc.]

Hi Jim,

Thanks for the reply. No, push notification are not enabled. If I click "Enable" (either in the auto-generated popup or /notifications/options/), it says "Enabling..." permanently (hence my previous "endless loop" comment). Here's the Browser Console error output when I click "Enable":

sendRemoveListener on closed conduit firefox-addon@expressvpn.com.2886218023767 ConduitsChild.jsm:112
    _send resource://gre/modules/ConduitsChild.jsm:112
    _send self-hosted:1282
    removeListener resource://gre/modules/ExtensionChild.jsm:670
    removeListener resource://gre/modules/ExtensionChild.jsm:905
    onChanged chrome://extensions/content/child/ext-storage.js:332
    removeListener resource://gre/modules/ExtensionCommon.jsm:2511
    revoke resource://gre/modules/ExtensionCommon.jsm:2533
    close resource://gre/modules/ExtensionCommon.jsm:2538
    unload resource://gre/modules/ExtensionCommon.jsm:899
    close resource://gre/modules/ExtensionContent.jsm:935
    destroyed resource://gre/modules/ExtensionContent.jsm:1011
    observe resource://gre/modules/ExtensionContent.jsm:1029

Again, this problem only affects Firefox.

[Mote Marketing, Inc.]

Any thoughts on this?

[Marc]

Do you have any plugins on your browser enabled that you can disable to test again? If not, I may need to get this tagged for a developer to take a look at for you