Android SDK 1.3.1 — 18 artifacts on Maven Central, with Jetpack Compose

MapConductor Android SDK 1.3.1 is on Maven Central — 18 artifacts, all at the same version, BOM included.

Using it

With the BOM you do not write a version for each module.

dependencies {
    implementation(platform("com.mapconductor:mapconductor-bom:1.3.1"))
    implementation("com.mapconductor:core")
    implementation("com.mapconductor:compose")
    implementation("com.mapconductor:for-maplibre")
}

If you do not use the BOM, still pin 1.3.1. 1.3.0 has the defect described below.

What was published

A few artifact names do not match their repository name. core and compose live in android-sdk-*, and geojson is still in android-geojson-layer — the Maven coordinate settled on geojson, and a published coordinate cannot be changed.

Jetpack Compose

com.mapconductor:compose is the Compose integration. The map is a MapView composable and the state lives in a state object; swapping providers does not change how you call it.

There is a second Compose-related reason to be on 1.3.1. The Compose BOM does not travel in a published POM. A BOM resolves versions during a build; it does not bake those versions into what you publish. 1.3.0 missed this, and shipped Compose dependencies with no version at all.

Use 1.3.1, not 1.3.0

When 1.3.0 was published, its POMs declared Compose dependencies without versions. Maven Central rejects that, so for-arcgis, for-here and for-tomtom failed to publish outright — but for-googlemaps, for-maplibre and for-mapbox went through broken. Consumers cannot resolve their Compose dependencies.

Published coordinates on Maven Central are immutable, so the fix went out as 1.3.1. Do not use 1.3.0.

Requirements

minSdk moved from 26 to 28, required by ArcGIS Maps SDK 300, which also sets compileSdk 37. Modules that do not use ArcGIS were raised too, because a single floor across the set is easier to live with than a per-module one.

Each module has its own repository under github.com/MapConductor.