Not supported by Swagger 2.0: Multiple operations with path 'v1/api/Admin/' and method 'POST'.

[stricq]

I installed Swashbuckle v5.5.2 in a new Web.API project that is .Net 4.6.1. With no controllers, it worked with no errors. However, after I added a controller with a Get and a Put method, I get the following error in Swashbuckle:

500 : {
"Message": "An error has occurred.",
"ExceptionMessage": "Not supported by Swagger 2.0: Multiple operations with path 'v1/api/Admin/' and method 'POST'. See the config setting - "ResolveConflictingActions" for a potential workaround",
"ExceptionType": "System.NotSupportedException",
"StackTrace": " at Swashbuckle.Swagger.SwaggerGeneratorOptions.DefaultConflictingActionsResolver(IEnumerable1 apiDescriptions)\r\n at Swashbuckle.Swagger.SwaggerGenerator.CreatePathItem(IEnumerable1 apiDescriptions, SchemaRegistry schemaRegistry)\r\n at Swashbuckle.Swagger.SwaggerGenerator.<>c__DisplayClass7.b__4(IGrouping2 group)\r\n at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer`1 comparer)\r\n at Swashbuckle.Swagger.SwaggerGenerator.GetSwagger(String rootUrl, String apiVersion)\r\n at Swashbuckle.Application.SwaggerDocsHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)\r\n at System.Net.Http.HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)\r\n at System.Web.Http.Dispatcher.HttpRoutingDispatcher.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)\r\n at System.Net.Http.DelegatingHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)\r\n at System.Web.Http.HttpServer.d__0.MoveNext()"
}
http://localhost:20923/swagger/docs/v1

The problem is, there is no Admin controller anywhere in the project. The controller I added does not have any POST methods at all.

[stricq]

I found the controller. It was coming from RavenDB DLLs.

[kdcllc]

@stricq How did you filter the RavenDB DLls? I am experiencing the same kind of issue.

I used this to resolve the issue: #142 (comment)

Thanks, kdcllc

[stricq]

I uncommented the ResolveConflictingActions line in the config.