Noibu is pleased to announce a major update to our error signature algorithm that targets issues with unidentified functions. Due to masking practices, earlier versions of the algorithm grouped these instances into signatures of the following formats:

file.js: cannot read properties of undefined (*)
file.js: cannot read properties of null (*)
file.js: undefined is not an object (*)
file.js: null is not an object (*)

In these signatures, * identifies a masked code element. Often, these masked elements do not include any personally identifiable information (PII), so we've revised the algorithm to collect and display the code in the error signature. As a result, instances of the generic, masked signatures will be deleted and replaced by more, specific signatures. Each signature will identify the code element associated with the error, and should include a complete error message without any masked elements.

Please note that this update has the superficial effect of creating more issues. However, this is a positive change. The new error signatures better identify the cause of each issue and provide more information to help you toward a resolution.

FAQ

1. I was working on an issue that will be affected by this change. What will happen to it?
   • The issue will be archived, but it will still be available to view with a link to the new issue(s).
     
     
2. Why has the ARL changed in the new issue(s)?
   • ARL may change because the specific error signatures allow Noibu to better attribute revenue loss to specific causes.