Processing

Please turn on custom prompt option along with prompt style radio button and select prompt style – 1 or prompt style -2. I have attached video of demo site. In future all browsers are going to have custom prompt subscription mandatory, so please always turn on custom prompt option and in the customize section turn on prompt style button and select prompt style -1 (horizontal ) or prompt style 2 (vertical)

I will also look into the problem why it stays when custom prompt style is off.

Thank you for your answer and sorry for my late reply!

On desktop (Mac) and FireFox, I can see the bell icon and subscribe without any issues now. However, when a user who is not yet subscribed visits their settings page / Push Notification subscription, the spinning wheel continues indefinitely, and no settings appear.

The same issue occurs on Android:
– The bell icon is not visible on mobile, but that’s acceptable as I already have a ‘Send Message’ button at the bottom right corner (from the Better Message plugin).
– So there’s no way to subscribe to notifications on mobile devices.

On iOS, I’ll need to ask a friend to test it, but I’d like to resolve the Desktop / Android issues first.

When Firefox is closed on desktop, no messages appears. Is it possible that a notification appears (Mac – Os / PC – Windows)?

• This reply was modified 1 month, 3 weeks ago by bartraymakers.
• This reply was modified 1 month, 3 weeks ago by bartraymakers.

I am looking into the front end subscription loader icon problem (under profile->settings->push notification subscription page).

For bell icon prompt in right side, i will add one more new option in admin settings page to move to left side or we can also override css class using WordPress custom css section to move to appropriate place where ever you want in the screen or shortcode is also available to display in side bar.

If browser is closed whether firefox/chrome and if corresponding browser service is disabled in computer (macos/windows) then it will also stop push notification services. Chrome will always will be active in background depending on your settings. Basically push notification will work only when corresponding service (whether it is desktop/mobile browser service or mobile app firebase push notification service) is active to poll for message in regular interval of time to receive and display notification. If Firefox service is active in background then push notification will work, suppose if Firefox is closed and if service is disabled in background then it will stop push notification service also. Please verify it in task manager list for active services.

I will release update in 2 days

Thank you for looking into it! I’ve encountered several additional bugs, which I believe you’ll find helpful in improving your product. I see great potential in this, and I hope this feedback contributes to its development.

• Group Subscription (Chrome/Mac): After clicking the ‘Subscribe’ button, I receive confirmation. However, when I check the group directory later, the ‘Subscribe push notification’ button reappears, indicating that I am not actually subscribed.
• Mobile/PWA App Subscription (Android): When subscribing on mobile (including the PWA app), I receive no confirmation. The page reloads, and the ‘Subscribe push notification’ button remains active.
• Android PWA App Notifications: While system notifications are enabled for the PWA app on Android, messages sent via the Better Message plugin do not trigger phone notifications. Notifications only appear when the app is opened. Additionally, there are no badge counts, nor do the notifications appear when I pull down the home screen (as with other notifications like emails).

There might be issues with my plugin settings or a problem on Firebase’s end, but I haven’t been able to identify any discrepancies.

Kind regards, Bart

I am looking into it on Group notification button and I will release new version on or before Monday

PWA app notifications are working as expected but still i will look into it, I will update you once new version is released.

Hello Mr. Murali,

I noticed that the plugin was updated to version 2.10 yesterday. After reinstalling the plugin, the app unfortunately still isn’t working properly.

• Notifications are received in the app itself, but not through the Android system. I checked the app notification settings in Android and they are set correctly.
• I can’t save push notification settings in the mobile app. Settings save correctly in a desktop browser. Everything is enabled, but the app shows all settings as inactive.

Perhaps you are still working on resolving issues, no problem at all!
I wanted to let you know about the error messages I see in the browser console:

pnfpb_icpush_pwa_sw.js:96 Service Worker: Installation failed.
pnfpb_icpush_pwa_sw.js:1 Uncaught (in promise) TypeError: Failed to execute 'addAll' on 'Cache': Request failed
Promise.then
(anonymous) @ pnfpb_icpush_pwa_sw.js:87
Promise.then
(anonymous) @ pnfpb_icpush_pwa_sw.js:84
pnfpb_icpush_pwa_sw.js:1 Uncaught (in promise) TypeError: Failed to execute 'addAll' on 'Cache': Request failed

These errors may be related.

Kind regards, Bart

I have tested in my demo site against Android PWA app as well as Android Native app(Java) both are working fine with PNFPB plugin using 2.10 version.

Please find embedded below 2 videos. 1. For PWA app push notification demo and 2. For Android native app push notification demo

Please always turn on custom prompt option because it is essentials for mobile browsers eventhough it is not related to your problem. Please also send me screenshot of your admin plugin settings or let me know what are all the options turned on. Since I am not able to replicate your problem using my demo site app, It will be helpful if you provide me settings which are using in your site like whether custom prompt turned on or off , bell icon prompt on or off…

Please make sure you cleared cache of your site, so that it will take latest version of CSS and Javascript changes(i already changed version of css and javascript in this version, it should take latest version automatically but in case if you have any cache or server cache please refresh it)

PWA app push notification demo (YouTube PNFPB demo video),

Android app push notification demo (YouTube PNFPB demo video)

I will also debug more tomorrow about service worker error in Android but at present my PWA app and Mobile app in Android are working as expected as shown in below 2 videos

• This reply was modified 1 month, 2 weeks ago by Murali.
• This reply was modified 1 month, 2 weeks ago by Murali.

@bartraymakers The plugin author made a serious mistake. Please confirm that you have changed your password and removed their account.

@murali-indiacitys You need to right now reply that you will never access a forum user’s site again or accept an offer to do that or you may be banned from this site and your plugin could be closed.

This is serious.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

Reply back that you understand the seriousness of this or you may lose access to this site.

Hello Jan,

The developper has never asked me for login credentials. I was the one asking how to provide it myself, for my staging website. All riscs are mine I guess. If I looked closely I would have found it myself.

You certainly can’t blame Murali for this. He is so helpful to me, I wish every developper has the same amount of patience. Most developpers aren’t as helpful as he is, and are after money.

So please, IF he did something wrong, give him all the benefits of the doubt, he has no wrong intentions, I trust him completely.

I have archived the replies as well but you did offer them admin access. And they did ask you to contact them using an email and informed you where to find it.

You certainly can’t blame Murali for this.

It’s not about blame, it’s about liability (the developer’s as well as yours) and responsibility. If the developer replies well and that they understand and commit to not repeating this then all will be good.

It’s just a mistake, we’re all human and we all make them including me.

They just need to reply well here is all and that’s that.

?I was the one asking how to provide it myself, for my staging website.

The prohibition applies to staging, test, non-production sites, etc. as well.

I will be more carefully next time.

I just hope that there are no further actions that can comprise the work of Murali. And that you don’t get this plugin offline.

Have a nice day! Kind regards, Bart

@jdembowski I did not ask for admin access or access to your site, As per policy I have never asked for access any user’s site till now, I am offering this plugin only for free with my own expenses till now for last 5 years. I asked only for screenshot or error messages which you are facing for push notification problem. To send screenshot of push notification settings, i asked to send it to my email id (only screenshots showing push notification settings or frontend console log messages to verify whether you configured Firebase). After that as mentioned above @bartraymakers replied to you with details. Please read my replies above i asked only for screenshot because i was not able to replicate those errors in my site, i thought due to some other external frontend plugins it might cause pwa cache problems, so due to this i asked for frontend or push notification settings screenshot not any other things.

@jdembowski Since i saw your messages today, I have replied with more details in slack stating that In future, i will deny login credentials from users and I apologize for confusion caused due to this.