-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
[🐛 Bug]: Selenium Manager unable to lookup Edge - Error parsing JSON #14851
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
Comments
@elliottj, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Also experiencing the same issue as Elliot, in my case using Selenium Webdriver 4.27.0 and Edge 130. |
Seeing the same issue, using selenium-manager 0.4.23 and Edge 131 |
I think it'll impact all versions of Selenium Manager if it's an unexpected change in the format of the data returned by https://edgeupdates.microsoft.com/api/products/ (ArtifactName vs artifactName) |
Can this issue be reproduced on other Operating Systems? |
Yes same on RHEL - given it's a change in the response from API call it will impact all OS and versions.
|
I will try to reproduce and work on fixing this. |
I have a fix. A PR will be open soon. |
* [selenium manager]: fix edge artifact deserialisation * add alias attr to all edge structs * add newline --------- Co-authored-by: Boni García <[email protected]>
When can we expect this fix in Live @bonigarcia ? |
It will be shipped in the next Selenium release (4.28). But if you need it now, you can download the new Selenium Manager binary from here: https://github.com/SeleniumHQ/selenium/actions/runs/12316815660 |
Thanks @bonigarcia |
@bonigarcia Thanks for fix, any idea when the next release will be please? |
Around the second week of January. |
The artifacts are expired, any other location available to get the latest selenium manager? Thanks! |
Try this https://github.com/SeleniumHQ/selenium/actions/runs/12538948126 |
Thanks! Downloading Edge now works. |
FYI, the older field names are now appearing in the API response, and downloading Edge seems to be working as expected. However, it’s unclear when this change was implemented by the Microsoft team. Users do not need to upgrade the Selenium version immediately. |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
What happened?
Running Selenium Manager Windows 0.4.27 command line to pull any Edge version shows:
When I look at https://edgeupdates.microsoft.com/api/products/ the json has an "artifactName" (lower case a at start), and only for the browser, not the webdriver - I'm not sure of the format SM expects?

How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
selenium-manager 0.4.27
What are the browser(s) and version(s) where you see this issue?
Edge all versions
What are the browser driver(s) and version(s) where you see this issue?
Edge all versions
Are you using Selenium Grid?
n/a
The text was updated successfully, but these errors were encountered: