X509TrustManager implements structure / crashlytics uncertainly?

Last week I received the shameful message "Your confirmation of the ssl certificate of your application is unsafe" [link] warning for our application.

Since we are not using a custom TrustManager, I looked at the apk application for the appearance of "checkServerTrusted". The only class that came up is related to Fabric / Crashlytics (most likely io.fabric.sdk.android.services.network.PinningTrustManager ).

Does anyone know if there is a problem with the implementation of Fabient TrustManager? Does anyone using Fabric (and not a custom TrustManager implementation) also get this warning?

I did not find the source code of the SDK, so I could not test myself, however, if you see similar results, in the next step I will contact their support.

Update:

+7
android google-play crashlytics fabric-twitter
source share

No one has answered this question yet.

See related questions:

219
How to disable Crashlytics during development
74
Crashlytics on iOS won't pass Build Your Project in Fabric app
42
Fabric / Crashlytics Integration via CocoaPods
39
How to initialize Crashlytics in Fabric.io?
thirty
Crashlytics Fabric: Failed to complete task
7
Install crashlytics without fabric?
6
Fabric / Crashlytics NoClassDefFoundError on specific devices only
4
Unable to load application in Fabric / Crashlytics
2
Reinstall crashlytics through fabric
0
Crashlytics / Fabric: disable notification for older versions of applications

All Articles