11 minutes ago, Marc said:

This is something we can go back and forth on all day. The actual answer is that it depends on the individual site

Yes, absolutely. But you know… this is the internet 😅

Does anyone have issues with push notifications for the app and the badge on the app icon? I'm not receiving anything despite notifications being sent via cron.

4 hours ago, PanSevence said:

Does anyone have issues with push notifications for the app and the badge on the app icon? I'm not receiving anything despite notifications being sent via cron.

Have you enabled Push in the notification settings area on your community? Open the notifications menu and tap the settings button to double check.

Also make sure that you’ve granted access to push notifications (and badges) in your device settings.

7 minutes ago, Ehren said:

Have you enabled Push in the notification settings area on your community? Open the notifications menu and tap the settings button to double check.

Also make sure that you’ve granted access to push notifications (and badges) in your device settings.

I did that it's even included in my report with a clip. I enabled push notifications in the app and granted the permissions.

There are so many factors that could prevent them from being delivered.

I was testing this a few weeks ago and spent hours debugging only to realise my phone had focus mode on, so no notifications were delivered. 99.99% of the time, it's the OS stopping them.

I have an iPhone and I've been using the PWA for a few weeks now, and always get notifications and notification count badges.

Something is probably blocking it. I'm not using Do Not Disturb mode. I've checked almost everything in my profile settings, push notifications are enabled, and I've allowed push notifications both in the app and in Chrome. Still, I'm not receiving any notifications.

Beta 3 is on it's way

This brings a few fixes and improvements to the PWA/web app.

This btw happend yesterday on test site with beta 2. Not sure why.

/index.php?app=core&module=system&controller=serviceworker&v=s3244590i3459345&type=admin

OutOfRangeException::0

#0 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(169): IPS\Patterns\ActiveRecord::load()
#1 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(73): IPS\core\tasks\viewupdates->update()
#2 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(444): IPS\core\tasks\viewupdates->{closure:IPS\core\tasks\viewupdates::execute():59}()
#3 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(59): IPS\Task->runUntilTimeout()
#4 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(343): IPS\core\tasks\viewupdates->execute()
#5 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(306): IPS\Task->run()
#6 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Dispatcher/Standard.php(355): IPS\Task->runAndLog()
#7 [internal function]: IPS\Dispatcher\Standard->__destruct()
#8 {main}

Btw in beta 3. Under manifest, the following items disapeard:

Display mode

• Full screen

  The website will be opened in fullscreen mode on the device and no user agent chrome (such as the address bar, navigational controls, or status bar) will be available.

• Standalone

  The website will be opened as a standalone application and minimal user agent chrome will be available (such as the status bar). This is the recommended mode.

• Minimal UI

  The website will be opened with minimal user agent chrome available similar to the standalone display mode, but will have more elements available such as navigational controls.

• Browser

  The website will be opened in the device's default browser.

53 minutes ago, Moestuin said:

This btw happend yesterday on test site with beta 2. Not sure why.

/index.php?app=core&module=system&controller=serviceworker&v=s3244590i3459345&type=admin

OutOfRangeException::0

#0 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(169): IPS\Patterns\ActiveRecord::load()
#1 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(73): IPS\core\tasks\viewupdates->update()
#2 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(444): IPS\core\tasks\viewupdates->{closure:IPS\core\tasks\viewupdates::execute():59}()
#3 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/applications/core/tasks/viewupdates.php(59): IPS\Task->runUntilTimeout()
#4 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(343): IPS\core\tasks\viewupdates->execute()
#5 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Task/Task.php(306): IPS\Task->run()
#6 /home/xxxxxxxx/domains/xxx.xxxxxxxx.nl/public_html/system/Dispatcher/Standard.php(355): IPS\Task->runAndLog()
#7 [internal function]: IPS\Dispatcher\Standard->__destruct()
#8 {main}

Please let us know if this happens on beta 3

39 minutes ago, Moestuin said:

Btw in beta 3. Under manifest, the following items disapeard:

Display mode

• Full screen

  The website will be opened in fullscreen mode on the device and no user agent chrome (such as the address bar, navigational controls, or status bar) will be available.

• Standalone

  The website will be opened as a standalone application and minimal user agent chrome will be available (such as the status bar). This is the recommended mode.

• Minimal UI

  The website will be opened with minimal user agent chrome available similar to the standalone display mode, but will have more elements available such as navigational controls.

• Browser

• The website will be opened in the device's default browser.

I've looped in Ehren on this in case its something intentional first of all. If not, we can get a bug report in for this one

Hi @Moestuin

Those settings were intentionally removed. When enabling the PWA, standalone is used.

On iOS, the only supported values are standalone and browser. The other values fallback to standalone, so including them as options in the ACP was quite pointless. Additionally, push notifications and splash images require standalone to be selected. So to prevent any confusion and to make the experience consistent across iOS and Android, the setting was removed in favour of always using standalone.

@PanSevence Do you use android, i do? Have been trying to get the notifications to work on there, also installed wpa app and then turned on push settings in notifications settings. But still don't see them. Also not using do not disturb. Also turned off battery saving for chrome.

Anything else i could try?

12 minutes ago, Moestuin said:

@PanSevence Do you use android, i do? Have been trying to get the notifications to work on there, also installed wpa app and then turned on push settings in notifications settings. But still don't see them. Also not using do not disturb. Also turned off battery saving for chrome.

Anything else i could try?

Yeah, use Android 15 for me push notifications not works. Have you performed tests on a system other than iOS?

No i have only android devices that i can test on.

I use push notifications with our sites all the time on Android 16 and MacOS via Chrome

@PanSevence Got it working on android. Besides turning on push notifications for browser. Also needed to check the Push checkbox for individual items for what items where allowed for the push notifications. For example for Private Messages.

35 minutes ago, Moestuin said:

@PanSevence Got it working on android. Besides turning on push notifications for browser. Also needed to check the Push checkbox for individual items for what items where allowed for the push notifications. For example for Private Messages.

Now they are also working correctly on my end.

17 hours ago, Matt said:

There are so many factors that could prevent them from being delivered.

I was testing this a few weeks ago and spent hours debugging only to realise my phone had focus mode on, so no notifications were delivered. 99.99% of the time, it's the OS stopping them.

I have an iPhone and I've been using the PWA for a few weeks now, and always get notifications and notification count badges.

Man, iphone focus screws me up all the time.

16 hours ago, Matt said:

Beta 3 is on it's way

This brings a few fixes and improvements to the PWA/web app.

Question on PWA, is it compatible with https://developers.google.com/codelabs/pwa-in-play#0

Then i could publish the forum app in google play store?

Edited July 30, 2025Jul 30 by Moestuin

On 7/25/2025 at 2:07 PM, ntxpla said:

It is not slow.

It is slow and I've posted proof of this in the past but here it is again. (the dcfc site was not on cloud at the time of recording but is now). When logged in on a cloud forum it really is sluggish like the Invision forum see the difference below compared to non cloud sites

Edited July 30, 2025Jul 30 by marklcfc

After an hour of tinkering got it working so it is compatible. Now i have a generated .apk file to upload to google playstore.

4 hours ago, Moestuin said:

After an hour of tinkering got it working so it is compatible. Now i have a generated .apk file to upload to google playstore.

I did that a long time ago I mastered the PWA application in TWA. Unfortunately, since Android 35+, there have been issues with edge-to-edge.

https://invisioncommunity.com/forums/topic/483975-twa-hides-android-system-ui-bottom-system-navigation-gestures-are-obscured/

12 hours ago, marklcfc said:

It is slow and I've posted proof of this in the past but here it is again. (the dcfc site was not on cloud at the time of recording but is now). When logged in on a cloud forum it really is sluggish like the Invision forum see the difference below compared to non cloud sites

You are comparing a site which is in debug almost constantly to sites in production elsewhere. I would fully expect our site would be slower in your comparison.

If you have issues with your cloud environment, please contact support. If you have specific feedback, please feel free to use the feedback forum provided.

On 7/23/2025 at 11:38 AM, Matt said:

PWA improvements

Heads-up: the PWA videos do not load. Tested in Edge, Firefox and Chrome.

And, since I just noticed this, a bug in the above highlight-quote. The link is not preserved.

Edited July 31, 2025Jul 31 by Como