How to use GetMessageID method of PuppeteerSharp.Connection class

I think you should not do a .ConfigureAwait on the controller level, look at this article for more information: https://blog.stephencleary.com/2017/03/aspnetcore-synchronization-context.html.

ASP.NET team dropped the use of SynchronizationContext, so using it in your controller is pointless.

As the article states, you should still use it on your service level, as you don't know whether or not a UI could plug itself to the service and use it, but on your WEB API, you can drop it.

The following code was working fine:

await page.WaitForSelectorAsync(".event"); // wait ajax completion
var divs = await page.QuerySelectorAllAsync(".event__header--no-my-games > .event__info");

foreach(var cd in divs)
{
   await cd.ClickAsync();
}

the problem was that the browser opened by Puppeteer had mobile dimension, in that case the selectors that I was looking for was differents.

I fixed that declaring a Viewport size in the following way:

Browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
      Headless = true,
      ExecutablePath = "your chrome path",
      DefaultViewport = new ViewPortOptions { Height = 1280, Width = 800}
});

this will open the site in desktop mode with correct selectors.

Hope this help someone.

System.ValueTuple was added in .NET 4.7. Upgrading your project to 4.7 would be easiest.

If you can't, but your project is targetting a version 4.5+ but less than 4.7, then you can install the System.ValueTuple NuGet package. If you run into any trouble there, see this answer.

After reading this issue, it seems that we should use absolute path with UserDataDir, so this works fine:

browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    UserDataDir = Path.Combine(AppDomain.CurrentDomain.BaseDirectory, ".local-chromium", "Win64-884014", "chrome-win", "UserData").Replace(@"\", @"\\")
});

But another problem appeared because browser doesn't save any cookie. Again, some issues on github said that the browser should be closed in order to save the cookies. I tried this:

await page.CloseAsync();
await browser.CloseAsync();

But it doesn't works as expected because the browser is still running in the background. The final solution for my was this:

var chromes = System.Diagnostics.Process.GetProcesses().Where(x => x.ProcessName == "chrome").ToList();

foreach (var ch in chromes)
{
    try
    {
        ch.Kill();
    }
    catch
    {
    }
}

The above code will close all chrome browsers, so it may need some changes in order to close the current browser only.

Add WaitForNavigationAsync() after your SetContentAsync() call to wait for the page content to load. By default it waits for the onLoad event, but you can use parameters to change it to wait for a different event.

await page.WaitForNavigationAsync();

First thing, you need to launch Chrome with remote debugging enabled. If you launch Chrome, for instance, with the flag --remote-debugging-port=2122, you know that you will be able to connect to the browser using the http://127.0.0.1:2122 URL.

Second, if you want to connect to an existing browser you need to call ConnectAsync instead of LaunchAsync.

Having all that. If would be a matter of doing something like this:

var browser = await Puppeteer.ConnectAsync(new ConnectOptions
{
    BrowserURL = "http://127.0.0.1:2122"
}));

If you want to automate a browser, then leave it open for user interaction, you will need to launch the browser before automating it, and have your code attach to that browser instance. This question gives some info on how to do that:

Puppeteer C#: Connecting to Running Chrome Instance

And this article goes into greater detail on that strategy:

https://medium.com/@jaredpotter1/connecting-puppeteer-to-existing-chrome-window-8a10828149e0

You have to be careful with your domain property. If it's not valid, it will be ignored. For what I see there. You might be setting something like http://www.yourdomain.com, when yourdomain.com is expected.

You might not be able to access to https://storage.googleapis.com/chromium-browser-snapshots/Win_x64/674921/chrome-win.zip.
If you can't access to that URL, you can try to download a Chromium 77 (or greater) manually, and use the ExecutablePath property to set the Chromium app location.