-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JavaScript runtime error: Object.keys: argument is not an Object error while using Swagger UI in IE 11. #2221
Comments
@disha-s - that's the version of Swashbuckle, not swagger-ui. Check the version at the top of the swagger-ui.js file. |
swagger-ui.js file has version 2.7.1. |
Can you verify that please? Current version is 2.1.4... 2.7.1 doesn't exist. |
where do i look for the version? |
Getting a similar error in ie11
The Swagger UI loads with all my endpoints but the security definitions have a problem so the 'Authorize' button doesn't show up. The top of the page hangs on |
Can you please confirm your versions for swagger-ui and swagger-js? Look in your swagger-ui.js file, you'll see something like this:
|
|
@bodnia can you please look at this? |
This is definitely an issue in IE11 for me as well. This is using the latest nuget package version of Swashbuckle 5+ as of August 4th. Looks like there may have been some commits, but it's still not readily available. |
@eavonius could you please confirm if you still can reproduce the issue with latest master? |
Please see a906cff |
to fix the IE issue, did you just add the es5-shim library to the repo and add it as a reference in index.html? |
@peyterkim this is correct |
I am getting the following error while using Swagger UI in Internet Explorer 11.
Unhandled exception at line 2, column 27219 in http://localhost:52697/service/help/swagger-ui.min.js
0x800a138f - JavaScript runtime error: Object.keys: argument is not an Object.
I am using "Swashbuckle.SwaggerUi": "6.0.0-beta9"
The text was updated successfully, but these errors were encountered: