Summary
Since 3.0.0, the base SDK is published to Maven Central as com.authgear:android-sdk:3.0.0, but the OkHttp interceptor module (sdk-okhttp) is not published there. There's currently no Maven Central coordinate a developer can add to get AuthgearInterceptor alongside the Maven Central base SDK.
Evidence
Base SDK is on Maven Central; the interceptor is not:
com.authgear:android-sdk -> HTTP 200 (repo1.maven.org)
com.authgear:android-sdk-okhttp -> HTTP 404
com.authgear:authgear-sdk-android-okhttp -> HTTP 404
In the source at tag 3.0.0:
sdk/build.gradle.kts uses the Vanniktech plugin with publishToMavenCentral() and coordinates("com.authgear", "android-sdk", …) → publishes to Central. ✅
sdk-okhttp/build.gradle.kts uses only id("maven-publish") with artifactId = "authgear-sdk-android-okhttp" (no publishToMavenCentral() / Vanniktech config) → not published to Maven Central.
So the interceptor (com.oursky.authgear.okhttp.AuthgearInterceptor) has no Central release to pair with android-sdk:3.0.0.
Impact
Suggested fix
Publish sdk-okhttp to Maven Central with the same tooling/versioning as the base module — e.g. com.authgear:android-sdk-okhttp:3.0.0 (Vanniktech publishToMavenCentral() + matching coordinates(...) and version), so the two artifacts stay in lockstep. Then the docs page can document the dependency.
Related (minor, separate)
The OkHttp doc's code sample mixes Java/Kotlin syntax (new OkHttpClient.Builder()....addInterceptor(AuthgearInterceptor(authgear))) and reads as incomplete — worth a small docs cleanup once the coordinate exists.
Context: found while modernizing the authgear-example-android sample (PR #5) and reconciling the Android docs.
Summary
Since
3.0.0, the base SDK is published to Maven Central ascom.authgear:android-sdk:3.0.0, but the OkHttp interceptor module (sdk-okhttp) is not published there. There's currently no Maven Central coordinate a developer can add to getAuthgearInterceptoralongside the Maven Central base SDK.Evidence
Base SDK is on Maven Central; the interceptor is not:
In the source at tag
3.0.0:sdk/build.gradle.ktsuses the Vanniktech plugin withpublishToMavenCentral()andcoordinates("com.authgear", "android-sdk", …)→ publishes to Central. ✅sdk-okhttp/build.gradle.ktsuses onlyid("maven-publish")withartifactId = "authgear-sdk-android-okhttp"(nopublishToMavenCentral()/ Vanniktech config) → not published to Maven Central.So the interceptor (
com.oursky.authgear.okhttp.AuthgearInterceptor) has no Central release to pair withandroid-sdk:3.0.0.Impact
Suggested fix
Publish
sdk-okhttpto Maven Central with the same tooling/versioning as the base module — e.g.com.authgear:android-sdk-okhttp:3.0.0(VanniktechpublishToMavenCentral()+ matchingcoordinates(...)and version), so the two artifacts stay in lockstep. Then the docs page can document the dependency.Related (minor, separate)
The OkHttp doc's code sample mixes Java/Kotlin syntax (
new OkHttpClient.Builder()....addInterceptor(AuthgearInterceptor(authgear))) and reads as incomplete — worth a small docs cleanup once the coordinate exists.Context: found while modernizing the authgear-example-android sample (PR #5) and reconciling the Android docs.