NaiboWang/EasySpider · error · Error

Element ${value} not found in any frame or iframe

Error message

Element ${value} not found in any frame or iframe

What it means

Thrown by findElementRecursive in the Electron main process (ElectronJS/main.js:219) after it has walked every <iframe> in the document and recursed into nested iframes without locating an element matching the Selenium locator. It is a plain JS Error (not selenium-webdriver's NoSuchElementException), raised only on the iframe=true code path.

Source

Thrown at ElectronJS/main.js:219

                            by,
                            value,
                            nestedFrames
                        );
                        if (element) {
                            return element;
                        }
                    }
                } else {
                    // If it is another exception, log it
                    console.error(`Exception while processing frame: ${error}`);
                }
            }
        } catch (error) {
            console.error(`Exception while processing frame: ${error}`);
        }
    }

    throw new Error(`Element ${value} not found in any frame or iframe`);
}

async function findElement(driver, by, value, iframe = false) {
    // Switch back to the main document
    await driver.switchTo().defaultContent();

    if (iframe) {
        const frames = await driver.findElements(By.tagName("iframe"));
        if (frames.length === 0) {
            throw new Error(
                `No iframes found in the current page while searching for ${value}`
            );
        }
        const element = await findElementRecursive(driver, by, value, frames);
        return element;
    } else {
        // Find element in the main document as normal
        let element = await driver.findElement(by(value));

View on GitHub (pinned to 191bd6d754)

Solutions

1. Confirm the target element and its iframe exist in the live DOM (DevTools Elements panel) and that the XPath still matches.
2. Add an explicit wait for the iframe to be present and for the element inside it before calling findElement (e.g. driver.wait(until.ableToSwitchToFrame(...)) then driver.wait(until.elementLocated(...))).
3. Make sure the page is fully loaded before the search; EasySpider uses pageLoadStrategy=none in some stages, so a manual wait or readyState check may be needed.
4. If the element is actually in the top document, drop the iframe=true flag so findElement uses the fast direct path.

Example fix

// before
let element = await findElement(driver, By.xpath, xpath, /*iframe*/ true);

// after - wait for iframe + element first
await driver.wait(until.elementLocated(By.tagName('iframe')), 5000);
let element = await findElement(driver, By.xpath, xpath, /*iframe*/ true);

// Validate iframe presence + element before the recursive search
async function iframeHasElement(driver, by, value) {
  const frames = await driver.findElements(By.tagName('iframe'));
  if (frames.length === 0) return false;
  for (const f of frames) {
    try {
      await driver.switchTo().defaultContent();
      await driver.switchTo().frame(f);
      const found = await driver.findElements(by(value));
      if (found.length > 0) return true;
    } catch { /* try next */ }
  }
  return false;
}

try {
  element = await findElement(driver, By.xpath, xpath, true);
} catch (e) {
  if (/not found in any frame or iframe/.test(e.message)) {
    notify_browser('xpath not found in iframes', 'xpath not found in iframes', 'warning');
    element = null;
  } else throw e;
}

When it happens

Trigger: Calling findElement(driver, by, value, iframe=true), which calls findElementRecursive. Inside, for each frame it does driver.switchTo().frame(frame) then driver.findElement(by(value)); on NoSuchElement it recurses into child iframes. When the frame list is exhausted with no hit, this Error is thrown.

Common situations: The XPath recorded by EasySpider points at an element inside an iframe that has not loaded yet; the page navigated and the iframe content is gone; the element is in a shadow DOM the traversal cannot reach; or the wrong node was marked with iframe=true during task design.

Related errors

• No iframes found in the current page while searching for ${v
• Element {value} not found in any frame or iframe
• No iframes found in the current page while searching for {va
• Elements with {value} not found in any frame or iframe
• dont parse timezone format

AI-assisted analysis of NaiboWang/EasySpider@191bd6d754 (2026-08-13). Data as JSON: /api/errors/92c5c6e33dbe6f47. Report an issue: GitHub.