Fixing the PWA “Update Available” Bar That Wouldn’t Stop Appearing

 ** If you find this helpful?  You can send a $5.00 donation to $vibeforge on Cash App. ** 

If you’ve been seeing the green “Update Available” bar appear over and over again, even when nothing major changed, I tracked down the cause and fixed it.

The issue turned out to be a mismatch in how the Progressive Web App (PWA) update system was behaving. The site was sometimes acting like a new update was waiting, while the service worker was already auto-activating in the background. In plain English: the site was basically saying, “An update is ready,” even when it had already started applying it.

That created a frustrating loop where the update bar would keep showing up more often than it should.

What was causing it?

The main problem was in the update notification logic inside the PWA manager script. The code was showing the update bar as soon as a new service worker finished installing, as long as there was already an active controller in place.

That sounds reasonable on paper, but the service worker itself was also configured to activate immediately by using self.skipWaiting() and then claim control right away with clients.claim().

So the system had two conflicting behaviors happening at once:

• The service worker was auto-activating immediately
• The UI was still showing a manual “Update Available” message

That combination made the site think there was always something new waiting, even when there really wasn’t.

What I changed

I cleaned up both the update notification logic and the service worker flow so updates now behave properly.

Files updated:

• modules/pwa/assets/js/pwa-manager.js
• sw.js

1) Fixed the update notification logic

Previously, the code would show the update message too early:

if (newWorker.state === 'installed' && navigator.serviceWorker.controller) {
  this.showUpdateNotification(registration);
}

I changed that so the green update bar only appears if there is an actual waiting service worker:

if (
  newWorker.state === 'installed' &&
  navigator.serviceWorker.controller &&
  registration.waiting
) {
  this.showUpdateNotification(registration);
}

This is important because it prevents the site from showing an update notice unless there is truly an update waiting to be applied.

2) Removed automatic activation on install

Inside sw.js, the service worker was forcing itself to activate immediately with this line:

self.skipWaiting();

I removed that so the update process can behave more predictably. Now the update bar and the service worker lifecycle are no longer fighting each other.

This creates a cleaner manual-update flow instead of a confusing half-automatic, half-manual one.

3) Cleaned up duplicate activate handlers

The service worker also had duplicate activate event handling, which can make debugging harder and sometimes causes inconsistent behavior.

I consolidated that into one clean activation handler so the service worker lifecycle is simpler and more reliable.

4) Bumped the cache version

I also updated the cache version from:

sngine-cache-v3

to:

sngine-cache-v4

This helps ensure the browser pulls in the fresh version cleanly instead of hanging onto stale cached files.

How the fixed behavior works now

With these changes in place, the green update bar should only appear when there is a real waiting update. It should no longer keep popping up repeatedly just because the service worker installed or refreshed in the background.

That means:

• No more false update prompts
• No more repeated green bar for no reason
• Cleaner service worker behavior
• More predictable PWA updates

Instructions after uploading the fixed files

1. Replace the old files with the fixed versions from the updated archive
2. Hard refresh your browser
3. If the site is installed as a PWA, fully close it and reopen it
4. If the old behavior still appears, open browser DevTools, unregister the old service worker one time, then reload the site

Final result

The constant green “Update Available” bar was not being caused by a real stream of updates. It was being caused by the way the service worker lifecycle and notification logic were interacting.

After cleaning that up, the PWA update system should now behave the way it’s supposed to: quiet when nothing is waiting, and only showing the update bar when there is a genuine update ready to apply.

If you are running a Sngine-based site with PWA support and have been seeing this same issue, this fix should make the update experience much smoother for both admins and users.

A quick thank you

I also want to take a moment to thank Jane Marcia Bezerra for continuing to provide the Sngine community with such thoughtful and useful addons. Contributions like hers help make the platform stronger, more flexible, and more valuable for everyone building with it.

If you use Sngine or benefit from community-built tools, please consider visiting the ScriptsTribe Addons Market and supporting her work with a purchase or even a donation. Supporting developers who invest their time and talent into the community helps ensure more great addons and improvements continue to be made.

Visit the ScriptsTribe Addons Market and support Jane’s work

 ** If you find this helpful?  You can send a $5.00 donation to $vibeforge on Cash App. **