Hi! Edit: You can pin to "3.3.0" (doesnt have to be 3.2.0) --  "3.3.1" is the version with the escaping issue. Can you try to pin the version @adobe/aem-headless-client-js to 3.3.0? I believe it might still be set to "^3.2.0" or "^3.3.0" which is letting your build pull in "3.3.1" which i think is i...

Hi - to work on assets in Creative Cloud apps, you need to download them to your device, process them, and then sync them back.  You can of course also explore AEM Desktop app [1] for syncing large sets of assets, processing them, and then syncing them back in bulk. [1] https://experienceleague.adob...

Yes - you can make the node with the sling:resourceType under /etc, /content, (or even /apps i think?) .. I would change the resource type tho since "MyProject/components/page" very much sounds like the resource is an AEM Page, rather than a controlled API endpoint. So maybe you declare: @SlingServl...

You will want to place ACLs on the resource that has that resource type (MyProject/components/page) -- so if you only want users in Group X to access this servlet, then deny jcr:read all on the node, and then allow jcr:read for Group X on that node.

Typically youd install BPA on a clone of production so you dont inadvertently effect Production as you prepare for the migration.

Does the request work on AEM Author? or if you hit AEM Publish directly? Are you sure that the Component Exporter is bound to the resource and working?

Hi, I assume youre talking about registering custom property Namespaces?   You can see this post on registering new property namespaces:    https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-assets/how-to-create-and-register-a-namespace-in-aem-as-a-cloud/m-p/453466/highlight/t...

Hi, If the issue wasn't fixed with the released fix, then youll have to check back with Adobe Support to see if it's been resolved in even later Service Packs (or you could look at the release nodes for subsequent SP). If not, then it sounds like the bug isnt fixed and you'd need to log a Support is...

Im not entirely certain (i dont have a Windows machine to test) but it looks like its failing (because it cant find the folder/file) to copy /D:/ACS-Rebuild/AEM_Branches/ACS/AEM/ui.apps/src/main/content/META-INF/vault/filter.xml' ... That makes some sense since it appears the Windows path is actuall...

AEM Gems have been relocated to Experience League! Keep watching for new Gems coming in the near future! https://experienceleague.adobe.com/docs/experience-manager-gems-events/gems/overview.html