🔄 Migration Guides

When upgrading between major or minor versions of the Veg Sahayyak SDK, you may encounter breaking changes or deprecated APIs. This guide provides step-by-step instructions to ensure a seamless transition for your integration.

📌 SDK Deprecation Policy

To support our B2B and enterprise clients, we adhere to a strict deprecation lifecycle:

1. APIs are never abruptly deleted.
2. Obsolete methods are marked with the @Deprecated annotation.
3. Deprecated methods are fully supported for exactly 2 major versions before being removed.
4. Your IDE will automatically suggest the ReplaceWith equivalent code.

---

Migrating from v2.1.0 to v2.2.0

Version 2.2.0 introduces the C++ Native Vault (libveg_vault.so) for offline cryptographic licensing.

1. TelematicsEngine Initialization Changed

Because the core math has been moved securely to C++, you can no longer instantiate TelematicsEngine directly without a license key.

🔴 Old Code (v2.1.0):

val engine = TelematicsEngine()

🟢 New Code (v2.2.0): You must now route all initialization through the SpeedAssistant builder and provide your JWT offline license key.

val speedAssistant = SpeedAssistant.with(context, "YOUR_JWT_LICENSE_KEY_HERE")

2. ProGuard Rules Update

If you are using R8/ProGuard for minification, you must add the new Native JNI rules so the C++ bridge is not stripped during compilation.

🟢 New Rule Required:

# Keep JNI bridge methods
-keep class com.vegsahayyak.speedcore.math.SpatialResolver { *; }
-keep class com.vegsahayyak.speedcore.math.LicenseManager { *; }