@shea8511 Are these all external dependencies and not provided by AEM? You can check each of these dependencies if they are already provided in /system/console/depfinder if you find an existing bundle, note the version and use this same version in your pom.xml dependencies section also add the scope...
@christopherv662 If you're using OSGi R6 annotations, error is probably beacuse @Reference annotation would not wrok as below. Try changing it to @OSGIService@referenceResourceResolverFactory resolverFactory;
@Vijayalakshmi_S React app is running in localhost (it's actually a firefly app). Below is the complete URL of the request. aem-upload sdk makes this call internally though I also tried making this call explicitly and get the same error (403). This same call with same authorization header works fin...
Thanks @Vijayalakshmi_S this works (somehow when I tried escaping earlier it did not work).For the development purposes for now, I've kept the crossorigin=* as testing from localhost and not actual adobe-static domain.Even though I don't get CORS error now but aem-upload sdk when trying to make ini...
@Vijayalakshmi_S- Yes th method is there but it doesn't work in localhost. So I'm trying to deploy it to cloud and now facing another issue. Config file appears here: /apps/<project-name>config/com.adobe.granite.cors.impl.CORSPolicyImpl~firefly.cfg.json but not in the system console so the changes a...
@aemninja Once you define various domains in externalizer, you would be able to refer those in the code as below:String myExternalizedUrl = externalizer.externalLink(resolver, Externalizer.LOCAL, "/my/page") + ".html";
Has anyone tried uploading a file from browser to AEM local sdk as well as AEM cloud via React application (node backend)? How do you get rid of the CORS error in the client?I tried below in react and it gives me CORS error even if I set the CORS policy config alloworgins to * const apiEndpoint = `h...