Repository navigation
7.1.0 unresolvable: com.sumup.pos.money.bundle:money:3.4.1 missing from maven.sumup.com — sample app also fails from fresh clone #282
Description
Activity
:)
Hey @saied-nawaz,
Thanks for opening this issue and for providing the detailed
dependencyInsightoutput.We reviewed the complete transitive dependency graph of the currently published
merchant-sdk:7.1.0,reader:7.1.0, andreader-offline:7.1.0artifacts, including all of theircom.sumupPOMs. We confirmed that none of the currently published modules declare a direct or transitive dependency oncom.sumup.pos.money.bundle:money:3.4.1.Since your
dependencyInsightoutput shows areader-offline:7.1.0 → money:3.4.1dependency that is not present in the current metadata, this suggests that stale dependency metadata is cached somewhere in your environment. Please note that a fresh Git clone does not clear Gradle’s global cache. The cache under~/.gradle/caches, as well as any Nexus or Artifactory proxy cache, persists across clones. This could also explain why the issue was reproducible with a fresh clone of the sample app.Could you please clear the cached metadata and try again?
./gradlew --stop rm -rf ~/.gradle/caches/modules-2/metadata-* ./gradlew clean build --refresh-dependenciesIf you use a Maven repository proxy such as Nexus or Artifactory, please also invalidate its cached metadata for the affected
com.sumupmodules. Otherwise, the proxy may continue serving the stale metadata to clean builds.If the issue persists, please share the fresh output from the following command so we can identify which configuration is still requesting the dependency:
./gradlew :app:dependencyInsight \ --configuration releaseRuntimeClasspath \ --dependency com.sumup.pos.money.bundle:money \ --refresh-dependenciesThanks @HeyPouya — confirmed. After clearing the cached metadata (
rm -rf ~/.gradle/caches/modules-2/metadata-*) and rebuilding with--refresh-dependencies,merchant-sdk:7.1.0resolves cleanly anddependencyInsightno longer shows any reference tocom.sumup.pos.money.bundle:money. The stale metadata in the global Gradle cache explains why it reproduced across fresh clones (the cache survives a fresh checkout). Full build and test suite pass on 7.1.0.Sorry for the noise, and thanks for the quick investigation — closing.
Upgrading
com.sumup:merchant-sdk7.0.0 → 7.1.0 per the official docs (single repohttps://maven.sumup.com/releases) fails:gradlew dependencyInsightchain:Notes from investigation (verified 2026-07-11):
merchant-sdk-7.1.0.aarandreader-offline-7.1.0.pomreturn HTTP 200 onmaven.sumup.com/releases, but no version of thecom.sumup.pos.money.bundlegroup exists there at all (maven-metadata.xml404), nor on Maven Central or Google Maven.maven.sumup.com/releasesrepo — which the sample'ssettings.gradle.ktsis also missing; the SDK isn't published togoogle()/mavenCentral()that it lists).Could you publish
com.sumup.pos.money.bundle:money:3.4.1tomaven.sumup.com/releases(and add the repo to the sample'ssettings.gradle.kts)? This currently blocks any fresh adoption of 7.1.0; we've had to stay on 7.0.0.