Crashlytics supports custom keys & logs to provide dynamic data with crash reports.
Per the API Docs, exceptions should be static, with dynamic data appended via custom keys

API Docs:
https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android#log-excepts
https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android#add-logs
Would you be open to a PR to support this feature once #335 is closed and this plugin migrates to the Crashlytics sdk instead of using the fabric sdk?
The migration to Firebase Crashlytics is now implemented on the dev branch (see here).
Please feel free to open a new PR against that code on dev.
@dpa99c Hi Dave, just a quick one. How are you testing crash on iOS? Ionic native wrapper function sendCrash works perfect for Android but in iOS, it doesn't seem to push crash to the console. Any thoughts? Thank you :)
@Roshankd1 I do all regression testing using the example project which is a known codebase designed as a test harness for validation of this plugin's functionality.
I can confirm that using it, I was able to see both iOS & Android crash data appear in the Crashlytics dashboard of the Firebase console using the new Firebase Crashlytics implementation in cordova-plugin-firebasex@10.
@dpa99c Thanks so much, will give it a try..Have a good day!
@dpa99c Hi Dave, Sorry I keep coming :D.. My GoogleService-Info.plist is being overridden by preset config values of firebase:
They get added once the iOS build is completed. Is this normal?
<key>FIREBASE_ANALYTICS_COLLECTION_ENABLED</key>
<string>true</string>
<key>FIREBASE_PERFORMANCE_COLLECTION_ENABLED</key>
<string>true</string>
<key>FirebaseCrashlyticsCollectionEnabled</key>
<string>true</string>