Value in JsonObjects name/value pair cannot be null
See original GitHub issueWhen resolving any identifier on https://dev.uniresolver.io/ I get the following error:
Error: Request failed with status code 500: Resolve problem for did:elem:EiAS3mqC4OLMKOwcz3ItIL7XfWduPT7q3Fa4vHgiCfSG2A: Value in JsonObjects name/value pair cannot be null
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
git - java.lang.NullPointerException: Value in JsonObjects ...
NullPointerException : Value in JsonObjects name/value pair cannot be null at org.glassfish.json.JsonObjectBuilderImpl.
Read more >java - How do you deal with NULL values while creating ...
In a JSON "object" (aka dictionary), there are two ways to represent absent values: Either have no key/value pair at all, or have...
Read more >Getting system information as JSON throws exception [Linux]
Hello, java.lang.NullPointerException: Value in JsonObject's name/value pair cannot be null at org.glassfish.json.JsonObjectBuilderImpl.
Read more >failover fails with a nullpointerexception with one vbond down
NullPointerException : Value in JsonObject's name/value pair cannot be null' Conditions: when the tunnel interface of a vbond is down ...
Read more >JsonObjectBuilder (JSON Documentation)
A builder for creating JsonObject models from scratch. This interface initializes an empty JSON object model and provides methods to add name/value pairs...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry it’s an internal bug following an update today… We’re working on fixing it.
Closing this since Im not seeing the error anymore. Thanks!