How to use FrameWaitForNavigationTests method of PuppeteerSharp.Tests.NavigationTests.FrameWaitForNavigationTests class

For anybody still encountering this issue, the answer by jamie-tillman on this github issue solved it for me:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
#####################
#PUPPETEER RECIPE based on https://github.com/hardkoded/puppeteer-sharp/issues/1180#issuecomment-1015532968
#####################
RUN apt-get update && apt-get -f install && apt-get -y install wget gnupg2 apt-utils
RUN wget -q -O - https://dl.google.com/linux/linux_signing_key.pub | apt-key add -
RUN echo 'deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main' >> /etc/apt/sources.list
RUN apt-get update \
&& apt-get install -y google-chrome-stable --no-install-recommends --allow-downgrades fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf
######################
#END PUPPETEER RECIPE
######################
ENV PUPPETEER_EXECUTABLE_PATH "/usr/bin/google-chrome-stable"
WORKDIR /app
EXPOSE 80
EXPOSE 443

The path to the executable is automatically detected by Puppeteer. However, I still had to disable sandboxmode as seen in the snippet below:

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = true,
    Args = new [] {
      "--disable-gpu",
      "--disable-dev-shm-usage",
      "--disable-setuid-sandbox",
      "--no-sandbox"}
});

More useful information is found in the issue thread so I recommend skimming through it if you still have trouble.

I think you will find easy to translate the code from puppeteer recorder to Puppeteer-Sharp. At least you can get the selectors from there.

Once you have those selectors you could do 3 things:

One option is setting a directory where the browser can store the cookies using the UserDataDir property. You could open the browser BrowserFetcher downloads and click that button.

A better solution is executing a script using EvaluateFunctionAsync to check if you have the cookies button and click it (using the selector you got from the recorder). Your code will be more flexible.

Last option would be downloading Chromie 77 or higher and launch it using ExecutablePath.

Change your Window_Loaded event method to async and do an await on the Init method, Event Handler methods are an exception. using async void instead of async Task is ok in this scenario. - Reference (Should I avoid 'async void' event handlers?):

private async void Window_Loaded(object sender, RoutedEventArgs e) 
{  
   await Handler.Init(Handler);
}

Set the Headless to true nad try

var options = new LaunchOptions
{
    Headless = true,
    ExecutablePath = @"C:\Program Files\Mozilla Firefox\firefox.exe",
    Args = argumentsWithoutExtension
};

Your main method does not wait for the result of your async call. The main method exits, closing the application. To fix it you need to wait for the async method to finish.

If you're using C# 7.1 or newer you can use async Main:

public class Program
{
    public static async void Main()
    {
        await TestAsync();
    }

    private static async Task TestAsync() 
    {
        await Task.Delay(5000);
    }
}

Otherwise you need to wait synchronously:

public class Program
{
    public static void Main()
    {
        TestAsync().GetAwaiter().GetResult();
    }

    private static async Task TestAsync() 
    {
        await Task.Delay(5000);
    }
}

The execution of the GetCookiesAsync task needs to be awaited, like this:

private async Task YourMethod()
{ 
    var result = await page.GetCookiesAsync();
}

You might need to change your callers for this.

Try to read about asynchronous programming in C#: https://learn.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/

So what you are seeing with this:

Id = 7315, Status = WaitingForActivation, Method = "{null}", Result = "{Not yet computed}"

is the async task not yet completed. GetCookiesAsync returns immediately. If you want to want to wait for the result, you should await it.

You can do something like this:

await page.EvaluateExpressionAsync("document.querySelectorAll('SCRIPT').forEach(e => e.remove())");

You can use the Response event:

var page = await browser.NewPageAsync();
page.Response += (sender, e) => 
{
    Console.WriteLine(e.Response.Url);
}

If you want to get an element from the browser you should get an ElementHandle, which is a pointer to an element in the browser, using EvaluateExpressionHandleAsync:

var element = await page.EvaluateExpressionHandleAsync($"document.querySelectorAll('[{attributeName}=\"{attributeValue}\"]')[0];");