Sometimes different issues are being grouped as the same issue in Crashlytics, even though the stack trace is different, with only the last line of the stack trace being the same.
The reason this is grouped is because production code, minifies the js file, resulting in all errors having the same line number (ie: 1).
Expected Behavior
The issues should be grouped separately
Actual Behavior
The issues are grouped together
Steps to Reproduce the Problem
Use a production codebase that minifies js.
Then cause different exceptions which is from the same js file
Specifications
Plugin version: Latest from master branch (25/1/2021)
Sometimes different issues are being grouped as the same issue in Crashlytics, even though the stack trace is different, with only the last line of the stack trace being the same.
The reason this is grouped is because production code, minifies the js file, resulting in all errors having the same line number (ie: 1).
Expected Behavior
The issues should be grouped separately
Actual Behavior
The issues are grouped together
Steps to Reproduce the Problem
Use a production codebase that minifies js. Then cause different exceptions which is from the same js file
Specifications