AEMaaCS SDK 2026.2 – /var/clientlibs resolves as NonExistingResource (RTE toolbar broken locally) | Community
Skip to main content
E
EduardoAEM
Level 1
February 25, 2026
Solved

AEMaaCS SDK 2026.2 – /var/clientlibs resolves as NonExistingResource (RTE toolbar broken locally)

  • February 25, 2026
  • 3 replies
  • 52 views

Hi all,

We are experiencing an issue in AEMaaCS SDK 2026.2.24288 where /var/clientlibs is not being resolved correctly in local environments.

 

Issue

In local SDK only (all developers, clean instances):

  • Requests to /var/clientlibs/... return 404

  • Sling resolves them as NonExistingResource

  • debugClientLibs=true fails (multiple 404 under /var/clientlibs/.../generated/*.css)

  • RTE toolbar does not render (including Core Components Text)

  • Console shows strict mode error:

Uncaught TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions
    at createRegisteredPlugins(...)
    at startEditing(...)

Cloud environments (DEV/STAGE/PROD) work correctly.

 

Clean Reproduction

  1. Delete crx-quickstart

  2. Start SDK:

java -Xmx4096m -jar aem-sdk-quickstart-2026.2.24288.20260204T121510Z.jar -r author

  1. Open:

http://localhost:4502/editor.html/... ?debugClientLibs=true

  1. Check:

http://localhost:4502/var/clientlibs/libs/cq/gui/components/authoring/dialog/richtext/clientlibs/rte/coralui3/css/generated/richtext.css

→ Returns 404
→ Request resolves to NonExistingResource

 

What we validated

  • HtmlLibraryServlet → ACTIVE

  • HtmlLibraryManagerImpl → ACTIVE

  • No unsatisfied OSGi components

  • Default ResourceResolver config

  • No permission issues

  • No custom project code required to reproduce

  • Happens on clean SDK

It looks like /var/clientlibs is not being handled virtually by the SDK runtime.

 

Question

Has anyone seen /var/clientlibs not being virtualized in SDK 2026.2?
Is there a known regression or missing feature flag related to virtual clientlibs handling in this version?
 

Any insight would be appreciated.

Thank you!

    Best answer by VishalKa5

    Hi ​@EduardoAEM ,

     

    In Adobe Experience Manager AEMaaCS SDK 2026.2, this issue is mainly related to a local SDK regression.

    Key Points:

    1. /var/clientlibs is a virtual path generated by HtmlLibraryManager, not a physical node.

    2. In SDK 2026.2, it may resolve as NonExistingResource, causing 404 errors.

    3. Because of this, RTE client libraries fail to load, and the RTE toolbar does not render.

    4. The issue happens only in the local SDK, while DEV/STAGE/PROD cloud environments work fine.

    5. Since it occurs even in a clean SDK instance, it is likely a SDK bug/regression.

    6. Recommended fix: update to a newer SDK version or use a previous stable SDK.

    Conclusion: This is not a configuration or project issue, but a known local SDK problem with clientlib virtualization.

     

    Thanks,

    Vishal

    3 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    March 2, 2026

    ​@Siva_Sogalapalli ​@Ritesh_Mittal ​@Raja_Reddy ​@sravs ​@Vijay_Katoch ​@Harwinder-singh ​@Mahedi_Sabuj Pulling you into the conversation in case you have seen similar scenarios and can share your experience to this thread.

    Kautuk Sahni
    VishalKa5
    VishalKa5Accepted solution
    Level 6
    March 11, 2026

    Hi ​@EduardoAEM ,

     

    In Adobe Experience Manager AEMaaCS SDK 2026.2, this issue is mainly related to a local SDK regression.

    Key Points:

    1. /var/clientlibs is a virtual path generated by HtmlLibraryManager, not a physical node.

    2. In SDK 2026.2, it may resolve as NonExistingResource, causing 404 errors.

    3. Because of this, RTE client libraries fail to load, and the RTE toolbar does not render.

    4. The issue happens only in the local SDK, while DEV/STAGE/PROD cloud environments work fine.

    5. Since it occurs even in a clean SDK instance, it is likely a SDK bug/regression.

    6. Recommended fix: update to a newer SDK version or use a previous stable SDK.

    Conclusion: This is not a configuration or project issue, but a known local SDK problem with clientlib virtualization.

     

    Thanks,

    Vishal

      AmitVishwakarma
      Community Advisor
      AmitVishwakarmaCommunity Advisor
      Community Advisor
      March 11, 2026

      Hi ​@EduardoAEM 

      This turned out not to be a project/config issue but a regression in the AEMaaCS SDK 2026.2.24288 itself.

      In this SDK build the virtual mapping for /var/clientlibs is broken, so:

      • /var/clientlibs/... resolves as NonExistingResource and returns 404
      • debugClientLibs=true fails
      • RTE clientlibs don't load -> RTE toolbar is broken
      • Cloud DEV/STAGE/PROD (AEM as a Cloud Service) work fine, only the local SDK is affected

      There is no OSGi or content-level fix you can apply locally – the only reliable solution is to run a different SDK version:

      • Stop AEM and delete the local crx-quickstart folder.
      • Start AEM with a known good SDK (for example the previous stable SDK you used before 2026.2.24288, such as 2025.12.x or 2026.1.x), or upgrade to a newer SDK once Adobe publishes a fixed build (2026.3+).

      After switching SDK, /var/clientlibs and the RTE toolbar work again as expected.

      Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
        Terms & ConditionsAccessibility statement

        Loading footer...