Hey @kautuk_sahni , Added the correct solution now.

The pipeline issue was resolved after certain rules were added. The primary problem stemmed from having a negative predicate rule, which required the inclusion of AEM-specific paths to ensure they were served correctly from AEM. With these adjustments, the product functional testing step has been su...

I’m currently working on creating the cdn.yaml file in AEM Cloud. The requirement is to include both traffic filters and origin filters. While the traffic filters are fine, I’m running into some issues with the origin filters.The requirements are as follows:www.test.com/pages/privacy – Should be ser...

Hi @MukeshYadav_ , Thanks for your input! I checked and noticed that my clientlibs were loading before the root element. After updating it, I can now see the React components successfully loading on my AEM page. 

@Shashi_Mulugu , No it is not SPA. I am trying to load clientlibs on the page but it is throwing this error :  **Uncaught Error: Minified React error #299; visit https://reactjs.org/docs/error-decoder.html?invariant=299 for the full message or use the non-minified dev environment for full errors and...

Hello, To simplify, let's use these keywords:- AEM Repo (Repo A)- Frontend Repo (Repo B)- React Repo (Repo C) I currently have an AEM repository (Repo A) that's already integrated with a Frontend repository (Repo B) using the aem-clientlib-generator. Now, I want to integrate a third repository, whic...