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.
every single logEvent console logging "invalid properties format" in v4.5.1
See original GitHub issuev4.5.0 doesn’t log like following, but v4.5.1 does
amplitude.js:2085 [Amplitude] Error: invalid properties format. Expecting Javascript object, received null, ignoring
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Log4j User Guide (PDF) - Apache Logging Services
1.1 Welcome to Log4j 2! 1.1.1 Introduction. Almost every large application includes its own logging or tracing API. In conformance with this.
Read more >Logging Configuration
To use the built-in adapters, set the hazelcast.logging.type property to one of the predefined types below: jdk: JDK logging (default). log4j: Log4j.
Read more >"items" param is not being shown in firebase console #4018
Issue Following the Docs we have a bunch of events that accept items param, according to the documentation it is an array of...
Read more >NLog 5.0 - List of major changes
When using LogEventBuilder for logging, then it will automatically captures callsite details with very little overhead with help from C# caller ...
Read more >Chapter 4: Appenders - Logback
It is responsible for outputting the logging events in a suitable format to the ... Each layout/encoder is associated with one and only...
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 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 submitted a pull request with a recommended patch.
@katsumeshi @nikchanda thanks for reporting, and apologies for the issue, we’ll have a fix going out soon