A similar issue was reported for Swashbuckle after updating to version 8.0.0. It appears to be caused by the browser caching the old version of swagger-ui.

The solution that worked for me was doing a forced refresh (Ctrl+F5) of the swagger page.