Hi,I think you are accessing incorrectly the resource, please check the proxy property from clientlibs: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/introduction/clientlibs#locating-a-client-library-folder-and-using-the-proxy-client-libraries-servl...

Hi,  The error indicates that you don't have a package-lock.json file, which can lead to dependency version collisions. Do you have a package-lock.json committed to your codebase? If not, please add it.   Hope this helps

Hi,  Launches work in a parent-child relationship, you cannot merge content between "siblings", however, you can create "nested" launches that will allow you to merge your changes to different targets(sources), so creating a nested structure can work for your use case. I am not sure if I understood ...

Hi, First, you should be aware that the classic UI is no longer supported by Adobe. Therefore, most people, including myself, would advise you to stop using the classic UI and switch to the Touch UI. Now, regarding your question, it seems like you might not be properly importing the necessary client...

@VeenaVikraman if you are referring to the core components, I think the best place to request such enhancements is directly in the GitHub repository https://github.com/adobe/aem-core-wcm-components/issues,

Hi,  I guess you are referring to the new Content Fragment Editor of AEM as a Cloud Service (AEMaaCS). This is a new UI that fully relies on the new sets of Content Fragment (CF) APIs that are publically available. The easiest way to troubleshoot what's going on is to understand which APIs are being...

Hi,  Are you seeing any issues in the browser console or on the logs? Would be possible to share a screenshot about the issue?

Hi @JakeCham    Yup, those steps are correct. Once you have done that, you will see in your Adobe Developer Console that the JWT credentials under the product you have updated are no longer being requested by AEM(or another application), once you confirm that, you are good to delete the JWT creds.  ...

Hi, The search is based on the properties (metadata) indexed by the damAssetLucene index, by default there is the list of specific metadata indexed, you can find those details here: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/search-assets#gql-se...

Try to remove all code from your instance, manually delete the code references via CRX/de, delete the packages installed in the package manager, and then redeploy your code. After completing these steps, make sure that your code functions correctly in the instance, that the bundle is active, and so ...