Skip to content

non-fatal errors shown with same text when calling indirectly #11474

@paulz

Description

@paulz

Description

For example we have a ErrorReporter protocol that is implemented in the main app by forward errors to Crashlytics.

We get this errors on the dashboard
image

which makes it look like errors happened inside ErrorReporter

Reproducing the issue

We use our ErrorReporter protocol to report errors, in tests to our error verifier and in production to Crashlytics.

Since we are not calling crashlytics directly from the code where error happened Crashlytics shows all errors happened in ErrorReporter:

image

• Non-fatal
FirebaseApp+Extensions.swift:19
protocol witness for ErrorReporterProvider.record(error:info:) in conformance FIRCrashlyti.

We would like to see actual error to be the title of the entry in the Crashlytics report.
as discussed here: #11452 workarounds we tried using Crashlytics.crashlytics().record(exceptionModel: exceptionModel) bring up other issues, like unable to provide userInfo.

Ideally we would like to be able to exclude fixed number of stack trace frames from appearing on the dashboard.

Firebase SDK Version

10.11

Xcode Version

14.3

Installation Method

Swift Package Manager

Firebase Product(s)

Crashlytics

Targeted Platforms

iOS, All

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions