Crashlytics custom keys are not deleted after sending a non-fatal exception

Step 1: Describe your environment

• Android Studio version: 4.1
• Firebase Component: crashlytics, messaging
• Component version: Crashlytics v17.2.1 | messaging v17.6.0

Step 2: Describe the problem

Crashlytics custom keys are not deleted after sending a non-fatal exception

Steps to reproduce:

1. I log some non-fatal exception with additional info (as described here: https://firebase.google.com/docs/crashlytics/customize-crash-reports?platform=android#log-excepts). Here is the function:

fun logNonFatalException(e: Exception) {
   if (e is MyCustomException) {
      FirebaseCrashlytics.getInstance().setCustomKey(e.key, e.value)
   }
  
   FirebaseCrashlytics.getInstance().recordException(e)
}

Then if any exception else happened, I will see next Crashlytics reports with all of the custom keys I added before.

[romanandreyvich]

Got it, thanks again.

[romanandreyvich]

My major problem is that I want to attach custom info to a particular exception and I have no idea how to do that in Crashlytics. Docs suggest to use custom keys so I tried to follow the advice and ended up with that issue: before recording the exception I add custom info using keys. After recording the exception I remove the keys. Since exception recording is async the keys are removed BEFORE the recording happens. I’m not sure I understand what issue should I create exactly? That I can’t attach custom info to an exception or that custom keys API doesn’t handle that case?