Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
NullReferenceException near Microsoft.Build.Logging.StructuredLogger.MessageProcessor.AddMessage(LazyFormattedBuildEventArgs, String)
See original GitHub issueAttempting to track down an issue in our build system we encounter the following error:
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Build.Logging.StructuredLogger.MessageProcessor.AddMessage(LazyFormattedBuildEventArgs args, String message)
at Microsoft.Build.Logging.StructuredLogger.Construction.CustomEventRaised(Object sender, CustomBuildEventArgs args)
This might be a duplicate of #351 however the issue is marked resolved as of 2.1.133 we are on 2.1.140. We have the log can can provide it privately if needed.
Thank you
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
No results found
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 Free
Top 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
I’ve just published 2.1.147 which uses
/bleven when you’re building in-app. This should hopefully prevent these errors from happening again.Seems to be working for us now, thank you for the quick turn around!