Firebase Crashlytics combines multiple DIFFERENT exceptions in one issue

Like this

[akaita]

Sorry it took quite long to get back onto OSS 🙇 .

Could you give me more details about this?
A test case would be best. Also, the complete stack-traces 🙏

[hannta]

Old issue but... I think this is more of on issue on Firebase Crashlytics side, not the way how this lib works.

Looks like Firebase Crashlytics groups exceptions by the method and line number where the exception was created.