You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PuppeteerSharp.NavigationException: 'Navigating frame was detached: NetworkManager failed to process Fetch.requestPaused. The JSON value could not be converted to System.String. Path: $.request.postData | LineNumber: 0 | BytePositionInLine: 85183.. at System.Text.Json.ThrowHelper.ReThrowWithPath(ReadStack& state, Utf8JsonReader& reader, Exception ex)
at System.Text.Json.Serialization.JsonConverter`1.ReadCore(Utf8JsonReader& reader, T& value, JsonSerializerOptions options, ReadStack& state)
at PuppeteerSharp.Cdp.NetworkManager.Client_MessageReceived(Object sender, MessageEventArgs e)'
Versions
PuppeteerSharp 20.0.4
.NET Core 3.1, .Net 9.0
Additional Information
20.0.3 works fine, but the e.MessageData in page.Client.MessageReceived sometimes throws the same exception when I try to convert it into a JSON string. I'm guessing it is related, but it's not a critical error as I can capture it. It seems that now the code in Client_MessageReceived is also trying to get at that data, and failing.
There was a change to PostData in 20.0.4, which is mentioned in the exception.
Description
Since 20.0.4 my code that uses SetRequestInterceptionAsync(true) can no longer load pages.
Complete minimal example reproducing the issue
Replace (dot) in the URL...
Expected behavior:
Page loads
Actual behavior:
GoToAsync causes an exception.
Versions
PuppeteerSharp 20.0.4
.NET Core 3.1, .Net 9.0
Additional Information
20.0.3 works fine, but the e.MessageData in page.Client.MessageReceived sometimes throws the same exception when I try to convert it into a JSON string. I'm guessing it is related, but it's not a critical error as I can capture it. It seems that now the code in Client_MessageReceived is also trying to get at that data, and failing.
There was a change to PostData in 20.0.4, which is mentioned in the exception.
#2810
My other issue also seems related:
#2775
The text was updated successfully, but these errors were encountered: