OpenApiRequestBody An item with the same key has already been added

[dannythomas13]

I have created a new Azure Function in VS2022 targetting .net 6 isolated and am now getting the following error: An item with the same key has already been added. Key: 'name of my parameter class'

The same code worked for a .net 6 Azure Function that was not running as an isolated process

[beukerz]

I have the same problem. It works find if you use a primitive type ie string. However if you use your own custom object it returns the error:

An item with the same key has already been added. Key: 'name of my parameter class'.

For example this works fine: [OpenApiRequestBody(contentType: "application/json", bodyType: typeof(string), Description = "Parameters", Required = true)]

And this returns an error: [OpenApiRequestBody(contentType: "application/json", bodyType: typeof(TestModel), Description = "Parameters", Required = true)]

The same issue exists for the OpenApiResponseWithBody. Please let us know what we can do to fix this.

[taipignas]

Same happens with the response attribute. I downgraded to Microsoft.Azure.Functions.Worker.Extensions.OpenApi 1.2.0 and the issue is gone.

An item with the same key has already been added. Key: mockSearchRequestDTO

http://localhost:7071/api/swagger.json at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at System.Collections.Generic.Dictionary2.Add(TKey key, TValue value) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](List1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector) at Microsoft.Azure.WebJobs.Extensions.OpenApi.Core.DocumentHelper.GetOpenApiSchemas(List1 elements, NamingStrategy namingStrategy, VisitorCollection collection) at Microsoft.Azure.Functions.Worker.Extensions.OpenApi.Document.Build(Assembly assembly, OpenApiVersionType version) at Microsoft.Azure.Functions.Worker.Extensions.OpenApi.Functions.OpenApiTriggerFunction.RenderSwaggerDocument(HttpRequestData req, String extension, FunctionContext ctx)

[klemmchr]

I'm having this issue using the response attribute together with a generic response type. As soon as I have two attributes with a different generic type I get this error:

An item with the same key has already been added. Key: apiResponse_iEnumerable1

A downgrade to 1.2.0 did not resolve my issue.

[CedNZ]

I have this same issue, downgrading to 1.2.0 (or building the latest source and using that) works for me

[CyberMutter]

Having the same issue after upgrading to version 1.3.0, downgrading to 1.2.0 works also for me.

[dannythomas13]

I hope it's not too much of a distraction from this conversation/issue but has anyone else noticed that the example (when we do get it to work using 1.2.0) wraps itself in quotes so that it is a string rather than json? The impact of this for me is that when using the test function of Azure APIM the payload is not valid and I have to manually remove the surrounding quotes and remove escape characters

https://github.com/Azure/azure-functions-openapi-extension/issues/444

[diogokunde]

Same issue here. Downgrade to 1.2.0 did not resolve too.

[msundquist-onebridge]

I'm also having this issue. Downgrading to 1.2.0 did fix the issue for me as well.

[brennfoster]

@justinyoo

There are a lot of duplicates regarding this issue now. I see that one duplicate has been closed with two linked PRs suggesting a fix has been made. (https://github.com/Azure/azure-functions-openapi-extension/issues/407)

Due to this other bug (https://github.com/Azure/azure-functions-openapi-extension/issues/387) I am unable to downgrade while we wait for the fix to be released.

This is becoming pretty urgent for us. Is it possible to get a patch with the fix?

[BronwenZ]

Same issue here. Can't downgrade to 1.2.0 due to (https://github.com/Azure/azure-functions-openapi-extension/issues/387)

[jeckyl2010]

@justinyoo

There are a lot of duplicates regarding this issue now. I see that one duplicate has been closed with two linked PRs suggesting a fix has been made. (#407)

Due to this other bug (#387) I am unable to downgrade while we wait for the fix to be released.

This is becoming pretty urgent for us. Is it possible to get a patch with the fix?

Same issues here - basically prevent us from automatically generating OpenAPI specs, which we use for autogenerating frontend TypeScript data contracts.

Is anyone aware of any alternative solutions, that work with Azure Functions v4, dotnet-isolated process and .NET 6.

Any ETA on when this will be fixed!!

[maurert]

I have the same issue in 1.3.0. (1.2.0 works fine.)

[jeckyl2010]

I'm wondering if the package development is stalled and if someone else have some better alternative packages to generate OpenAPI documentation for .NET 6 Azure Function projects using dot-isolated coding scheme.

[brennfoster]

I just discovered that if I move the custom object into a separate project then the open api extension renders the swagger document successfully.

Sharing for anyone still struggling with this and needing a work around.

[Dongbumlee]

Hey @brennfoster, I really regret I found your thread so lately. I had to spend a whole day to find work around. I confirmed it works! Really appreciate it. 👍🏻

hopefully it can be fixed in next release.