Perfectly solve the problem that Android studio cannot compile after integrating crashlytics

Problem Description:

The following error occurs during compilation after integration with fabric:,

Error:Cause: hostname in certificate didn't match: <maven.fabric.io> != <*. motili.com> OR <*.motili.com> OR <motili.com>

Partial script of build.gradle (automatically generated by fabric plug-in):

Take a closer look at that https://maven.fabric.io/public The certificate of the website (as shown in the figure below). The website specified in the certificate is *. Motili.com. It is obviously wrong. I don't know how this plug-in is generated.

Studio is requesting https://maven.fabric.io/public The certificate verification cannot be completed, so an error is reported directly, and the HTTPS certificate verification cannot be removed in settings.

Then send an e-mail to support asking why, and reply after 3 days. The reply is as follows:

There is no actual content. Is the response of support too slow, or does support pay no attention to this crashlytics at all.

Cause of problem:

https://maven.fabric.io/public Unable to access (the certificate does not match), in fact, just change this website. If you find it later, you can change it to: https://twittersdk.artifactoryonline.com/twittersdk/public

Build.gradle can be directly replaced by:

In addition, some personal feelings about using crashlytics:

1. The fabric.io interface has complete crash analysis functions. Unfortunately, there is no anr / Caton detection, which is a little weak.

2. Although there are studio plug-ins, the integration speed of studio is too slow. Foreign websites often can't go up. Anyway, the plug-in hasn't responded for a long time by clicking the button

3. Gradle compilation connection is also very slow to download AAR library. Be patient

4. Landing fabric.io is too laggy to view data, and it is too slow to respond. Developers who want to go in quickly to view data are rather unfriendly.

5. The interface layout is a little too complicated. Many times, users are overwhelmed and don't know where to go.

6. I collected some crash codes that are somehow garbled, and I can't see the original data

The above article perfectly solves the problem that Android studio cannot compile after integrating crashlytics. It is all the content shared by Xiaobian. I hope it can give you a reference and support more programming tips.