Repository navigation
Releases
2.0.0
Core Android SDK 2.0.0. Major version: some response accessors changed type (cautionDirections, plotShape, tracedGeometry, VastuJobItem.input). Adds the capture-merge types that vedika-sdk-android-ar 1.2.0 needs, plus portfolio, collaboration, job artifacts, device attestation, delete receipts, richer errors and idempotency routing. Full changelog in README.md.
Install: com.github.vedika-io:vedika-sdk-android:2.0.0
Real-phone accuracy not yet measured.
1.1.1
The bundled offline Vastu runtime sends the API key as Authorization: Bearer instead of x-api-key. No API change. x-api-key is still accepted by the API.
1.1.0
Vastu job methods (submit with Idempotency-Key, status, results, cancel), 2xx response handling, device attestation on upload.
Vedika Android SDK 1.0.4
Fixes the JitPack build (Error status on 1.0.0-1.0.3).
Root causes:
- No committed Gradle wrapper: JitPack fell back to its own bootstrap Gradle 4.8.1 to generate one, and that Gradle version cannot start under the JDK 17 JitPack already installs (
ScriptPluginFactory/PluginResolutionStrategyInternalcrash). - No
maven-publishplugin, so JitPack'spublishToMavenLocaltask did not exist. - The default artifactId (
vedika-android-sdk, from this Gradle module's project name) did not match this repo's name (vedika-sdk-android), so the coordinatecom.github.vedika-io:vedika-sdk-androidwould never have resolved even after a successful build. - JitPack's default build image sets
ANDROID_HOMEbut ships no platform under it, so packagingVastuArView(which needsandroid.jar) failed there too.
Fixed by committing a Gradle 8.10.2 wrapper, adding maven-publish with the artifactId pinned to vedika-sdk-android, and adding jitpack.yml to pin JDK 17 and bootstrap Android SDK platform 34 into JitPack's build image.
Install:
repositories { maven { url = uri("https://jitpack.io") } }
dependencies { implementation("com.github.vedika-io:vedika-sdk-android:1.0.4") }1.0.3
AR compass: when the phone is held upright, the heading now follows the back camera instead of the screen's top edge, so it no longer changes with display rotation. Previously a phone held sideways with rotation lock on could read about 90 degrees off. Verified on Pixel 8 and Pixel 8 Pro to within 0.13 degrees in every rotation.
Flat phones keep the top-edge behaviour, with hysteresis between the two modes and no 180-degree jumps.
1.0.2
Vastu scan calls (save, retrieve, list, delete, timelapse) no longer send an Idempotency-Key: the API identifies a scan retry by scanId or the body's requestId and rejected every scan call carrying one with 422 IDEMPOTENCY_CONTRACT_UNSUPPORTED. Passing a key to a scan call now fails before sending, and scan calls are still retried on transient errors. Response types now include notAssessed (spaces with no placement rule, never graded) and the other new Vastu response fields; the offline runtime carries the heading-provider fixes. No breaking changes except that an explicit idempotency key on a scan call is now refused.
1.0.1
The bundled offline Vastu runtime now applies the WMM2025 magnetic declination returned by the API, so VastuArView reports true-north headings. Source comments no longer reference internal documents. No API changes. Build from source with gradle jar, or take the attached jar.
1.0.0
First release of the Vedika Android SDK.
Native Kotlin client for the Vastu API surface and the native AR view. OkHttp + Kotlin, JDK 17, with a versioned offline AR runtime bundled as a resource so VastuArView needs no network fetch on first load.
A plain kotlin("jvm") library, so it builds and unit-tests on a bare JDK with no Android SDK installed, and an Android app consumes it like any other JVM dependency.
Build from source with gradle jar, or take the attached jar.
Mirrored from the Vedika monorepo; sdks/android/ there remains the source of truth.