Puppeteer: Attempted to use detached Frame

A Frame object in Puppeteer represents one frame in the page tree: the main frame or an iframe. When that frame is removed from the page, Puppeteer marks the object as detached, and any later call on it (evaluate, $, click, waitForSelector, or calls on handles that belong to it) throws this error. The quoted value is Chrome's internal frame ID.

It appears in two situations. With iframes, the embedding page removed or rebuilt the iframe, which is common with payment fields, captcha widgets and ads. With the main frame, it usually means the whole page or tab was closed or swapped, often because the script kept using a page object after the site opened a new tab and closed the old one, or after the browser crashed.

What is not wrong: the selector or code you were running inside the frame.

async function payFrame(page) {
  const el = await page.waitForSelector('iframe[name="card"]', { visible: true });
  return el.contentFrame();
}

const frame = await payFrame(page);
await frame.locator('input[name="cardnumber"]').fill('4242424242424242');

Look frames up by a stable attribute every time you need them instead of storing Frame objects. Wait for third-party widgets to finish rendering before typing into them. If a site opens new tabs, track them with browser.waitForTarget() and switch explicitly.