Running multiple instances of puppeteer while having both user-data-directory and profile-directory defined

Steps to reproduce

Tell us about your environment:

• Puppeteer version: v1.6.2
• Platform / OS version: MacOS High Sierra 10.13.6
• URLs (if applicable): n/a
• Node.js version: v8.2.1

What steps will reproduce the problem?

Please include code that reproduces the issue.

const puppeteer = require('puppeteer');

// payload.settings.chromeProfile = `default` || `Profile 1`
// payload.settings.chromeDir = `/Users/userName/Library/Application Support/Google/Chrome/`

let appConfig = {
  width: 960,
  height: 900,
  deviceScaleFactor: 1
};

let args = {
  args: [
    '--no-sandbox',
    '--disable-setuid-sandbox',
    '--disable-infobars',
    '--window-position=0,0',
    '--ignore-certifcate-errors',
    '--ignore-certifcate-errors-spki-list'
  ]
};

let userAgent = 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36';

args.headless = false;

// assign chrome profile path
// enable sync with account
let specialArgs = [`--profile-directory=${payload.settings.chromeProfile}`, '--enable-sync'];

// ignore default flags
args.ignoreDefaultArgs = [
  '--password-store=basic',
  '--enable-automation',
  '--disable-sync',
  '--safebrowsing-disable-auto-update',
  '--disable-background-networking'
];
args.args.push(...specialArgs);

args.executablePath = '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome';
args.userDataDir = payload.settings.chromeDir ? payload.settings.chromeDir : null;

(async () => {
  try {
    const browser = await puppeteer.launch(args);
    const page = await browser.newPage();
    await page.setViewport(appConfig);
    await page.setUserAgent(userAgent);
    
    await page.goto('https://www.google.com/', {
      waitUntil: 'networkidle2'
    });

   // run actions...
  } catch (error) {
    console.log(error);
    await browser.close();
  }
}

What is the expected result?

I should be able to launch each new instance of a browser with it’s defined profile intact and have it execute its defined actions without messing up the other browser instances.

What happens instead?

The following ends up happening:

1. Execute the first instance of puppeteer with a profile defined.
2. While the first instance is running, I execute another instance with either the same or new profile.
3. The second browser pops up with the correct profile, but only opens a new blank page and stops running any additional actions.
4. Once the new blank page opens on the second browser, the first browser re-runs the actions again.

I’ve tested this without setting any profile-directory path and it works correctly.

[connorjclark]

@xerxesj Why did you close this - did you find a solution? I’m coming across the same issue now.

[rinogo]

Ditto. Why was this closed? Any ideas from the community? I’m think it might have something to do with using tabs vs. windows. I think we might only be able to actively process the active tab. My code seems to be opening separate tabs which may be part of the problem…