Issue with Super PWA

  • Resolved snakejac

    (@snakejac)


    2 years, 2 months ago

    I just upgraded some components in my wordpress including PHP version to 8.1, Elementor and surely some other plugins, and now i experience issue with Super PWA that the banner add to home screen did not show up when i turn on the super page cache, but if i turn off the super page cache but still put the A Name domain proxied in Cloudflare, the banner add to home scree for pwa working

    i dont know to to track or debug the issue of this matter, everything seems work just fine when i try to debug using Chrome Tools

    Can anyone suggest me how to do it properly to resolve this issue?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    Hi @snakejac,
    Can you share your website URL and also the steps to replicate the issue? Cause add to homescreen option comes from the manifest.json file and this plugin has nothing to do with the file. Are you seeing soe error in the browser console?

    Thread Starter snakejac

    (@snakejac)

    Hi @isaumya thanks for the prompt response,i couldnt share the url for some confidentiality issues with our client if you mind

    But i would like to share the error message through web dev tools chrome as follow

    superpwa-sw.js:4 SuperPWA: Current request is excluded from cache.
    jquery-migrate.min.js:2 JQMIGRATE: Migrate is installed, version 3.3.2

    5superpwa-sw.js:4 SuperPWA: Current request is excluded from cache.
    register-sw.js:1 Registration failed with SecurityError: Failed to register a ServiceWorker for scope (‘https://my.abc.com/’) with script (‘https://my.abc.com/superpwa-sw.js&action=bypasscache’): The script does not have a MIME type.
    19superpwa-sw.js:4 SuperPWA: Current request is excluded from cache.
    jquery.min.js:2 [Violation] ‘orientationchange’ handler took 352ms

    [Violation] Forced reflow while executing JavaScript took 348ms
    swiper.min.js:13 [Violation] ‘resize’ handler took 150ms
    comment-reply.min.js:2 [Violation] Added non-passive event listener to a scroll-blocking ‘touchstart’ event. Consider marking event handler as ‘passive’ to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
    d @ comment-reply.min.js:2
    o @ comment-reply.min.js:2
    [Violation] Forced reflow while executing JavaScript took 69ms

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @snakejac,
    Looking at the errors mentioned above, I don’t see that the issue is coming from this plugin.

    BTW, are you using the plugin with ?swcfpc=1 cache buster query parameter? If so, please make sure that you have updated the plugin to the latest version and then go to the Other tab inside the plugin settings, scroll down to the section Remove Cache Buster Query String and you will see a hyperlink there for the Implementation Guide.

    Follow the implementation guide and add the Cache Rules in your Cloudflare Account. (Don’t add the 4th optional cache rule).

    Check if your issue gets resolved after removing the Cache Buster Query String.

    Thread Starter snakejac

    (@snakejac)

    hi @isaumya , I am currently using Worker Mode, before that i use the non worker mode and set the cache buster query string , but it didnt work quite well, somehow i got problem with some css and js script, is it because of the CF? because when i turn of the plugin and un proxy the website, everything works jsut fine

    Thread Starter snakejac

    (@snakejac)

    Hi @isaumya don’t add 4th optional rule for cache buster query string means Rule 4 ? Cache Eligible Requests & Ignore Query Params from cacheKey?

    Plugin Contributor iSaumya

    (@isaumya)

    Hi @snakejac,
    Go back to using page rule mode by disabling the worker mode inside the plugin settings. Then add the cache rule and then enable the remove cache buster query string option.

    Yes. don’t add the Rule 4. Just add rule 1, 2, 3

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Issue with Super PWA’ is closed to new replies.