JitPack is included in the default Android
build.gradle
under
allprojects.repositories
, which makes Gradle query it for all dependency resolution — even packages like BouncyCastle that only exist on Maven Central.
JitPack went down for 24+ hours (March 8-9, 2026) with no communication, completely blocking Android builds for all Expo projects. The failure happens because
expo-updates
depends on BouncyCastle via a version range, and Gradle times out trying to fetch metadata from JitPack.
This wasn't just us — many projects were affected (jitpack/jitpack.io#7836).
JitPack appears minimally maintained at this point (no status page, no incident communication), and Maven Central + Google's Maven repo cover all core dependencies. If specific Expo packages still need JitPack, they could declare it in their own module-level
build.gradle
with content filtering instead of polluting the global repo list.
Would love to see JitPack removed or at least scoped in the default template so a third-party outage can't block all Android builds.