Android build failing: cannot connect to maven.fabric.io

Expo Development Tools
1

I’ve had two Android builds fail just now with the logs below.

I need to ship a new release, how can this be fixed?

Download https://repo.maven.apache.org/maven2/org/abego/treelayout/org.abego.treelayout.core/1.0.1/org.abego.treelayout.core-1.0.1.jar
WARNING: Configuration 'provided' is obsolete and has been replaced with 'compileOnly'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html
[stderr] FAILURE: Build failed with an exception.
[stderr] * What went wrong:
[stderr] A problem occurred configuring project ':expoview-abi25_0_0'.
[stderr] > Could not resolve all files for configuration ':expoview-abi25_0_0:classpath'.
[stderr]    > Could not resolve com.android.tools.build:builder:3.1.4.
[stderr]      Required by:
[stderr]          project :expoview-abi25_0_0 > com.android.tools.build:gradle:3.1.4 > com.android.tools.build:gradle-core:3.1.4
[stderr]       > Could not resolve com.android.tools.build:builder:3.1.4.
[stderr]          > Could not get resource 'https://maven.fabric.io/public/com/android/tools/build/builder/3.1.4/builder-3.1.4.jar'.
[stderr]             > Could not HEAD 'https://maven.fabric.io/public/com/android/tools/build/builder/3.1.4/builder-3.1.4.jar'.
[stderr]                > Connect to maven.fabric.io:443 [maven.fabric.io/13.249.143.149] failed: connect timed out
[stderr]    > Could not resolve org.ow2.asm:asm-analysis:5.1.
[stderr]      Required by:
[stderr]          project :expoview-abi25_0_0 > com.android.tools.build:gradle:3.1.4 > com.android.tools.build:gradle-core:3.1.4
[stderr]       > Could not resolve org.ow2.asm:asm-analysis:5.1.
[stderr]          > Could not get resource 'https://maven.fabric.io/public/org/ow2/asm/asm-analysis/5.1/asm-analysis-5.1.pom'.
[stderr]             > Could not HEAD 'https://maven.fabric.io/public/org/ow2/asm/asm-analysis/5.1/asm-analysis-5.1.pom'.
[stderr]                > Connect to maven.fabric.io:443 [maven.fabric.io/13.249.143.149] failed: connect timed out
[stderr]    > Could not resolve org.ow2.asm:asm-commons:5.1.
[stderr]      Required by:
[stderr]          project :expoview-abi25_0_0 > com.android.tools.build:gradle:3.1.4 > com.android.tools.build:gradle-core:3.1.4
[stderr]       > Could not resolve org.ow2.asm:asm-commons:5.1.
[stderr]          > Could not get resource 'https://maven.fabric.io/public/org/ow2/asm/asm-commons/5.1/asm-commons-5.1.jar'.
[stderr]             > Could not HEAD 'https://maven.fabric.io/public/org/ow2/asm/asm-commons/5.1/asm-commons-5.1.jar'.
[stderr]                > Connect to maven.fabric.io:443 [maven.fabric.io/13.249.143.149] failed: connect timed out
[stderr]    > Could not resolve net.sf.proguard:proguard-gradle:5.3.3.
[stderr]      Required by:
[stderr]          project :expoview-abi25_0_0 > com.android.tools.build:gradle:3.1.4 > com.android.tools.build:gradle-core:3.1.4
[stderr]       > Could not resolve net.sf.proguard:proguard-gradle:5.3.3.
[stderr]          > Could not get resource 'https://maven.fabric.io/public/net/sf/proguard/proguard-gradle/5.3.3/proguard-gradle-5.3.3.jar'.
[stderr]             > Could not HEAD 'https://maven.fabric.io/public/net/sf/proguard/proguard-gradle/5.3.3/proguard-gradle-5.3.3.jar'.
[stderr]                > Connect to maven.fabric.io:443 [maven.fabric.io/13.249.143.149] failed: connect timed out
[stderr] * Try:
[stderr] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[stderr] * Get more help at https://help.gradle.org
[stderr] BUILD FAILED in 2m 40s
2

It looks like this issue is happening sporadically but not consistently across the board. I’d recommend trying again and seeing if things are better now.

3

It worked the 4th time, so I’m unblocked for now, but it was definitely a pain as we couldn’t release on the day that we wanted to.

There’s also a warning in the same logs that state that some resource is deprecated and going away in 2018, but I can’t find it now. Worth looking at.

4

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.