This does not solve our issue. Not sure why it is marked as "Correct answer" and "accepted solution"

the same issue here on AEM Version 6.5.13.0 (after update from 6.5.9.0) "Move" button is inactive in Touch UI: If I remove "disabled" attribute from the (QueryResultImpl.java:85) at org.apache.jackrabbit.oak.jcr.query.QueryResultImpl.getRows(QueryResultImpl.java:83) at com.day.cq.search.impl.builder.QueryImpl$RowIterable.iterator(QueryImpl.java:833) at com.day.cq.search.impl.builder.QueryImpl.execute(QueryImpl.java:649) at com.day.cq.search.impl.builder.QueryImpl.getResult(QueryImpl.java:111) at...

The component is enabled. See screenshot in my comment of 21/10/2021 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/unable-to-add-building-blocks-to-custom-template-in-experience/m-p/428552/highlight/true#M122016 Same story as with Saiteja120, ‎30-12-2019 01:32 PST saying "Yes, checked in custom Template also. It's added in Policy."

Hi Arun, I've converted a piece of Ex.Fr. into a building block, but I can't drag it to the container. Placeholder doesn't get highlighted with blue frame - it doesn't recognise that I am dragging a building block.

Why do I need to drag and drop? Because it is a basic functionality.https://helpx.adobe.com/experience-manager/kt/sites/using/building-blocks-experience-fragment-feature-video-use.htmlwatch from 4:22In my case the component is "enabled" on the Experience Fragment template, but I can't drag and drop or see the component in the list. (though I can see "Layout Container" and all other enabled components)

What do you mean by "directly use" ? The component exists in AEM for usage within Experience fragments. The issue is "Unable to add Building Blocks".. to experience fragment.

Hi Arun,exactly. And also I am not able to select it via "+" button, as this component is not displayed in the list of available components, although it is added to the template structure as one of the allowed components. Error log on Author has following records, but those records are unlikely a result of any user action:21.10.2021 16:18:38.774 *DEBUG* [ip-address 1634793518773] GET /libs/cq/experience-fragments/editor/clientlibs/buildingblocks.min.js HTTP/1.1] com.onepath.core.filters.LoggingF...

Not sure why the answer is marked as correct,@arunpatidar. Has this fixed the problem?In our case, of course the component is allowed on a template, it just doesn't appear as available in the list of components on experience fragment variation editor and you can't drag and drop a Building Block into the variation container.

Thanks Feike,it makes sense now. Very helpful.