Clientlibs donot get updated | Community
Skip to main content
L
lipishree
March 29, 2022

Clientlibs donot get updated

  • March 29, 2022
  • 3 replies
  • 2372 views

We have been facing issues with Clientlibs update. Every time we push new changes to the existing clientlibs, after deployment , it still shows the older one. We are using AEM as cloud, and have tried rebuilding the Clientlibs/clearing the clientlib cache(/libs/granite/ui/content/dumplibs.rebuild.html), but this doesnt work.
The workaround is to always update new category name for the client lib, and thus it identifies a new client lib altogether when deployed.

Isn't AEM already versioning and rebuilding clientlibs. Any support please.

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    3 replies

    Vijayalakshmi_S
    Vijayalakshmi_S
    Level 10
    March 29, 2022

    @lipishree 

    Versioned/serialized hash URL is enabled/available by default in all cloud service environments. The same is updated when the underlying CSS/JS is changed. 

    Could you please 

    • cross check the clientlib URL as included in the page before and after deployment. 
    • check the changes in Incognito after deployment 
      Himanshu_Jain
      Community Advisor
      Himanshu_JainCommunity Advisor
      Community Advisor
      March 31, 2022

      Same issue and tried the methods which you mentioned above but no success.

      Himanshu Jain
        Himanshu_Jain
        Community Advisor
        Himanshu_JainCommunity Advisor
        Community Advisor
        March 31, 2022

        Check which specific clientlib version is creating issue .

        Also check the special character in that particular css files ( check formatting) .

        Hope it will help.

        Himanshu Jain
          ManviSharma
          Adobe Employee
          ManviSharmaAdobe Employee
          Adobe Employee
          April 4, 2022

          As per my understanding, the issue is happening because clientllibs are not recompiled at the later stage of the deployment. When the clientlib is compiling it will look for the included CSS file.

           

          Here you can try below: 

           

          -->The first approach, avoid deleting the CSS files at the initial deployment by excluding the file paths in filter.xml. 

           

          -->The second approach is to include the clientlib along with the CSS files in the later stage of the deployment. Hope this resolves your issue. 

            Terms & ConditionsAccessibility statement

            Loading footer...