http://blog.csdn.net/zhuobattle/article/details/50555393
Problem Description:
After integration with fabric, the following error has occurred,
Error:Cause:hostname in certificate didn ' t match: <maven.fabric.io>! = <*.motili.com> OR <*. motili.com> OR <motili.com>Build.gradle Partial scripts (automatically generated by the fabric plugin):
Buildscript { repositories { maven {URL ' https://maven.fabric.io/public '} } dependencies { Classpath ' io.fabric.tools:gradle:1.+ ' }}apply plugin: ' com.android.application ' Apply plugin: ' Io.fabric ' Repositories { maven {URL ' https://maven.fabric.io/public '}}
Take a closer look at the Https://maven.fabric.io/public website certificate (such as), the site specified in the certificate is *.motili.com, obviously wrong, do not know how this plugin is generated.
Studio failed to complete the certificate verification in the request Https://maven.fabric.io/public, so the direct error, and the settings to remove the HTTPS certificate is not possible.
Then send the support email to ask why, after 3 days to reply, reply content as follows:
[HTML]View PlainCopy
- Hey there,
- is chance connecting through a proxy server, or is you behind a firewall?
- Cheers,
- Bear
- Helpful? Click to give Bear Douglas thanks!
There is no actual content, is the support response too slow, or support simply has not attached importance to this piece of crashlytics.
Cause of the problem:
Https://maven.fabric.io/public cannot access (certificate does not match), then in fact, as long as the URL to replace it, the following found can be replaced by:
Https://twittersdk.artifactoryonline.com/twittersdk/public
Build.gradle Direct replacement can be changed to:
[Java]View PlainCopy
- Buildscript {
- repositories {
- Maven {URL ' https://twittersdk.artifactoryonline.com/twittersdk/public '}
- }
- dependencies {
- Classpath ' io.fabric.tools:gradle:1.+ '
- }
- }
- Apply plugin: ' com.android.application '
- Apply plugin: ' io.fabric '
- repositories {
- Maven {URL ' https://twittersdk.artifactoryonline.com/twittersdk/public '}
- }
Another personal use of crashlytics some feelings:
1. Fabric.io interface, Crash Analysis function is full, unfortunately there is no anr/test, this piece is a bit weak.
2. Although there are studio plug-ins, but the studio integration speed is too slow, foreign sites are often not go, anyway, that plugin point button half a day did not respond
3.gradle compile connection It's very slow to download the AAR library, so be patient.
4. Login Fabric.io View data is sometimes very card, too slow, for the developers to go quickly to see the data is very unfriendly
5. The interface layout is a bit too miscellaneous, many times let the user at a loss, do not know where the point.
6. Collect some crash somehow garbled, can't see the original data
Issues that cannot be compiled after Android studio integrated Crashlytics