selenium: webdriver.getCurrentUrl throw a exception[πŸ› Bug]:

What happened?

An exception occurred when I used the getcurrentUrl interface

How can we reproduce the issue?

if(!pluginOpen.isSucess()){
            return pluginOpen;
        }
        final String currentUrl = driver.getCurrentUrl();
        //登录鑡青
        if(StringUtils.equalsIgnoreCase(currentUrl, LocalContant.loginUrl )){
            //θ·³θ½¬εˆ°η™»ε½•ι‘΅ι’
            return login(driver);
        }
        //已经登录了
        if(StringUtils.equalsIgnoreCase(currentUrl, LocalContant.homeUrl )){
            return TaskCompleteModel.ok("η™»ε½•ζˆεŠŸ");
        }

Relevant log output

ChromeDriver was started successfully.
org.openqa.selenium.WebDriverException: unknown error: Runtime.evaluate threw exception: Error: LavaMoat - property "swb_bdoWpoasnfa93pfcPOmcfL_Promise" of globalThis is inaccessible under scuttling mode. To learn more visit https://github.com/LavaMoat/LavaMoat/pull/360.
  at get (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/runtime-lavamoat.js:11200:17)
  at callFunction (<anonymous>:443:26)
  at e.<computed> (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sentry-install.js:1:677)
  at <anonymous>:460:23
  at e.<computed> (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sentry-install.js:1:677)
  at <anonymous>:461:3
  (Session info: chrome=105.0.5195.147)
Build info: version: '4.8.1', revision: '8ebccac989'
System info: os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_202'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Command: [9b6c092513dfa44a0ac64e0886583949, getCurrentUrl {}]

Operating System

win10

Selenium version

4.8.1

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

chrome

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

chrome 105

Are you using Selenium Grid?

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

Then the issue is related to the plug-in, not Selenium itself. Can you reproduce the issue only with Selenium?