-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonDecodingException when Cookie.expires is null #494
Comments
Thank you for opening this issue, and even more for reporting this to the protocol definition project. I'll see if I can somehow add some opt-in lenience for this. Not sure if it can be done, but if I can add a workaround I definitely will. |
Interestingly, the error I'm getting is this one instead:
Maybe another bug in the protocol definitions? Weird. |
Looks like this is just a recent change in the protocol. This field used to be a string, and now it's defined as an object, but I guess I'm not testing against the most recent version of chrome (the |
I experimented with Browserless and their Docker image instead of That said, since your initial request is valid, I am adding some pre-processing to make I will also need to change a bit the entrypoint of the library to support directly providing web socket URLs in a more convenient way, so people can work with Browserless more easily. |
Version
5.14.0-1299070
What happened?
Getting an exception when decoding a message with a
Cookie
that hasexpires
set tonull
like the one below. I think the actual issue is that the Chrome DevTools Protocol, not settingexpires
as an optional. I have reported the issue, but maybe there is something that can be done in the Kotlin library?Exception:
Reproduction and additional details
Steps to reproduce:
Kotlin target platforms
macOS, Linux
The text was updated successfully, but these errors were encountered: