• Resolved tenacityio

    (@tenacityio)


    The plugin appears to cache CSS files in the ServiceWorker.

    A hard refresh and cache clear in Chrome will display the correct files, but it isn’t persistent in the ServiceWorker. So once you refresh the page the old CSS is displayed again.

    Here is a screenshot of the network panel; you can see that the caching is disabled. But CSS is still being loaded from the ServiceWorker
    https://help.tenacity.io/xQuOnjrb

    Here is a screenshot of the network panel after a Clear Cache & Hard Refresh.
    https://help.tenacity.io/GGuJ64Dv

    But once you refresh the page again, back to the ServiceWorker.
    https://help.tenacity.io/8Lugkpmw

    Is there a way to clear that cache? Or stop it from doing that?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hello

    The OneSignal SDK file https://cdn.onesignal.com/sdks/OneSignalSDKWorker.js is cached for around 3 days. This file gets updated regularly since push changes very frequently we push out updates to make sure everything is current.

    We won’t be able to change this, but if you want to setup your own cacheing rules for this file, you can. We suggest caching this file for no more than 1 week.

    Let us know if you have any additional questions.

    Thanks

    Thread Starter tenacityio

    (@tenacityio)

    @onesignal To be clear, it’s the CSS files that the Service Worker is caching that matter to us and causing issues.

    Is there no way to clear those or prevent them from being cached?

    Why does a push notification script need to cache CSS?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Caching CSS Files’ is closed to new replies.