We are also facing similar issue. @webdev91  Did you find any code solution for this?

Yes we do have corressponding react component and have mapto for that too. I also checked same for wknd-spa-react project(demo that AEM folks has provided). Same issue is also happening on their custom component and hello world component.

For our site , we think experience fragment can be good choice for some work.When I created Experience fragment in react SPA app, I can use some generic components but can not use my custom component.I can see those components available to add but when I add it , we do not see anything in UI(in expe...

Able to resolve this issue via following method.Added 3 js scripts and css links in external site ( clientlib-react.js,container.js,clientlib-base.js,clientlib-react.css)in index,js where we initialize modelmanager, had to give our rootpath as an argument.(since our site was within external site, de...

we have used vanity URL feature provided by AEM, worked pretty well for us

We are also facing similar issue, when we updated page policy in templated , we can see that component available on page but when we add it on page , nothing happens

Hi team, Our web lives within another team's website. we are recreating our site with AEM 6.5 React SPA and wanted to check about approch for itegration. If it is react only app, we can include script tags along with matching div name and that should work but since it is AEM app seems like there is ...