This is a old question, but I got the same in NET 8.0 with Swagger 6.9. and 6.8. The problem was resolved, cleaning the browser cache. To see if this the problem opens your application swagger in an incognito window.