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
First of all, thanks for your effort in maintaining this repository.
I've recently started to get an error on every incoming message from the server (last week I would say, although I am not sure because I've been on vacations). After some debugging, the issue seems to be caused by incoming messages not having the field "as_der" in "data" -> "leaf_cert" -> "as_der", which causes a null pointer in CertStreamCertificate.java, line 37, if statement.
I imagine this is due to a recent change in the message format. My current workaround is to surround the above-mentioned if statement with a pojo.asDer != null check, but I am not sure if that would be the optimal solution.
I would appreciate if you could take a look at the error and provide me some feedback.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
with
"My current workaround is to surround the above-mentioned if statement with a pojo.asDer != null check, but I am not sure if that would be the optimal solution."
Do you mean:
Hello,
First of all, thanks for your effort in maintaining this repository.
I've recently started to get an error on every incoming message from the server (last week I would say, although I am not sure because I've been on vacations). After some debugging, the issue seems to be caused by incoming messages not having the field "as_der" in "data" -> "leaf_cert" -> "as_der", which causes a null pointer in CertStreamCertificate.java, line 37, if statement.
I imagine this is due to a recent change in the message format. My current workaround is to surround the above-mentioned if statement with a
pojo.asDer != null
check, but I am not sure if that would be the optimal solution.I would appreciate if you could take a look at the error and provide me some feedback.
Thanks in advance!
The text was updated successfully, but these errors were encountered: