[🐛 Bug]: bug not fixed for "selenium seems to override _", issue 12659

[Jabbar2010]

What happened?

just report a bug from code level, no demo here, but can look at this issue: https://github.com/appium/appium-remote-debugger/issues/383#issuecomment-2165253340

How can we reproduce the issue?

if a website used loadash, it will be reproduced

Relevant log output

_.clone is not a function

Operating System

Mac OS 14.5

Selenium version

4.19.0

What are the browser(s) and version(s) where you see this issue?

the latest

What are the browser driver(s) and version(s) where you see this issue?

the latest

Are you using Selenium Grid?

no

[github-actions[bot]]

@Jabbar2010, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[github-actions[bot]]

Hi, @Jabbar2010. Please follow the issue template, we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided, thank you.

[titusfortner]

We made a change to our code so Appium could build the atoms it needs. That change caused some problems for Selenium users, so we restored the previous code. But Appium is still using the atoms generated during that period, so if there is a conflict, I'm pretty sure it is in the Appium atoms. If there is a bug here, it's that we can't build the atoms Appium needs with the current code after rolling back the last change, but that's getting tracked elsewhere