Feature Request: CrashlyticsLogWriter should allow setting the FirebaseCrashlytics instance #426
Replies: 2 comments
-
I believe this would require updates to CrashKiOS which would be a fair bit of work. I would start with an issue on there first. |
Beta Was this translation helpful? Give feedback.
-
This is, in fact, something that would need to happen first in the CrashKiOS layer. Moving to discussions. CrashKiOS itself needs some refactoring, as the way the Kotlin compiler links has changed since it was designed. In addition, the Crashlytics support itself was changed dramatically. All calls now happen through ObjC's dynamic invocation. How that is accomplished would certainly complicate passing in different Crashlytics instances (although maybe not much. Would need to look at it). |
Beta Was this translation helpful? Give feedback.
-
Currently CrashlyticsLogWriter uses
FirebaseCrashlytics.getInstance()
internally to obtain an instance ofFirebaseCrashlytics
. This call uses the defaultFirebaseApp
instance.However in our app we have multiple Firebase projects and therefore configure
FirebaseApp
manually in code. We need the possibility to pass in an instance of eitherFirebaseApp
orFirebaseCrashlytics
so that logs end up in the correct Firebase project.One way could be that
CrashlyticsCallsActual
optionally takes this instance and thatCrashlyticsCalls
becomes a constructor argument ofCrashlyticsLogWriter
.Note: This is written from the viewpoint of an Android application. iOS should probably receive this feature, too.
Beta Was this translation helpful? Give feedback.
All reactions