Curious -- what happens if you downgrade EPiServer.Find.Cms to 14.0.4, and keep EPiServer.ContentDeliveryApi.Search @ 3.5.0?
Daniel Issaacs, I've set your answer as the Accepted Answer because it does immediately resolve the issue and hopefully going forward that can turn around a fix for this.
For this project I have chosen to ommit the EPiServer.ContentDeliveryApi.Search package as we will have our own designed API for search.
FYI: Fixed in Find 14.2
The content will be published, but a validation error is returned with the following message:
My Service Extension for setting up Content Delivery API is as follows:
Steps attempted to resolve the Issue:
For now I've removed EPiServer.ContentDeliveryApi.Search from my client's project, but retained EPiServer.ContentDeliveryApi.Cms. It's not a deal breaker for us to keep the Content Delivery Search API out of the solution as we would also include our own Search APIs tailored to the client's needs. I would add that while the EPiServer.ContentDeliveryApi.Search package was installed, it otherwise appeared to function as expected and it is just the publishing of content that we observed as causing us an issue.
For reference, here are the other packages that were installed:
EPiServer.CloudPlatform.Cms @ 1.0.5
EPiServer.CMS @ 12.10.0
EPiServer.ContentDeliveryApi.Cms @ 3.5.0
EPiServer.ContentDeliveryApi.Search @ 3.5.0
EPiServer.Find.Cms @ 14.1.0
EPiServer.Labs.BlockEnhancements @ 1.1.1
Geta.NotFoundHandler.Optimizely @ 3.0.1
Geta.Optimizely.Categories @ 1.0.0
Geta.Optimizely.ContentTypeIcons @ 2.0.1
Geta.Optimizely.Sitemaps @ 2.0.0
MediatR @ 10.0.1
MediatR.Extensions.Microsoft.DependencyInjection @ 10.0.1
Stott.Security.Optimizely @ 0.2.0-beta
Swashbuckle.AspNetCore @ 6.4.0
Swashbuckle.AspNetCore.Annotations @ 6.4.0