AdminConsole
← All SDKs and distributions
React Native · Source SDK

Mapmyindia Intouch React Native SDK

A Mappls sdk for tracking telematics, workforce, gis analytics, identity platform across React Native.

deprecatedDo Not Startstateful
Do Not Start

Compatibility decision

Do not start a new production build from this evidence. Contain existing use, identify a supported target, migrate with rollback, and retire the dependency.

Repository content, activity, code fragments, and local correspondence are discovery evidence only. They do not establish a supported package coordinate, binary identity, current version, account entitlement, runtime pairing, production compatibility, or approval.
PlatformReact NativeGroovy · Text · JavaScript
Source activityAgingLast repository push 2024-11-21
CorrespondenceExact1 minimized local candidates; candidates are not compatibility proof
Captured documentation27 sections10 source samples · 17 endpoint signals
Scope

Products and prerequisites

GIS & Analytics
  • A React Native project with both native build environments
  • OAuth client credentials issued for the intended Mappls project
Captured source evidence

Install and configuration guidance

These statements are reproduced as normalized repository evidence. Validate coordinates and versions before copying them into a project.

4 matching sections

Setup

We use your Client ID to identify your account details and assign all your user's devices under a single account.

To get your Outh2 Rest API Client ID and Client Secret please login to MapmyIndia API Dashboard

Please contact apisupport@mapmyindia.com to get InTouch SDK access to your Client ID

After getting the access, you can start with the InTouchDemo app, or Integrate the InTouch SDK in your app.

Getting started

Install the below mentioned library in your project.

npm install mapmyindia-intouch-react-native-sdk --save

• If using React-native<0.60 react-native link mapmyindia-intouch-react-native-sdk

Installation

For Android and Ios add the below mentioned lines

Step 3: Initialize Intouch SDK

Initialize the SDK with your Client ID and Client Secret and device name.Device name helps to identify the user on Portal.

Sanitized repository fragments

Source code evidence

Use these fragments to understand integration shape. They may belong to an older toolchain or authentication generation.

6 shown
AndroidGroovy
allprojects {
   repositories {
            mavenLocal()
            maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
           url("$rootDir/../node_modules/react-native/android")
            }
           maven {
 // Android JSC is installed from npm
    url("$rootDir/../node_modules/jsc-android/dist")
          }

  
+       maven { url 'https://maven.mapmyindia.com/repository/mapmyindia/'}

           google()
           jcenter()
           maven { url 'https://www.jitpack.io' }

         }

}
AndroidGroovy
defaultConfig {

applicationId "com.intouch_react_native_sample"

minSdkVersion rootProject.ext.minSdkVersion

targetSdkVersion rootProject.ext.targetSdkVersion

versionCode 1

versionName "1.0"

+ multiDexEnabled true

}
Step 1: Import Intouch SDKJavaScript
import  MapmyIndiaIntouch  from  'mapmyindia-intouch-react-native-sdk';
Step 2. Check if Intouch SDK is already initializedJavaScript
const  status = await  MapmyIndiaIntouch.isInitialized();
Step 3: Initialize Intouch SDKJavaScript
MapmyIndiaIntouch.initialize(deviceName,clientId,clientSecret)
   .then(entityId  => {
   console.log(entityId);
   }).catch(err=>{
     console.log(err.message)
   });
Step 4: Check if Intouch SDK is already runningJavaScript
const  status = await  MapmyIndiaIntouch.isRunning()
From discovery to release

Connected implementation paths

Exact source paths

No quickstart or starter explicitly names this source. Continue through the platform path without claiming direct lineage.

Release gate

Production compatibility checklist

A clean demo is the beginning of the decision, not its conclusion.

  1. 01

    Confirm the exact package or artifact identifier and version with the owning Mappls product team; a repository name is not a package contract.

  2. 02

    Verify platform toolchain, operating-system, architecture, host-application, and transitive-dependency compatibility from a clean build.

  3. 03

    Bind only the documented credential class and restriction to its intended client or trusted-server runtime; never commit or log a secret.

  4. 04

    Verify account entitlement, region, quota, endpoint generation, data rights, and applicable commercial terms independently.

  5. 05

    Exercise initialization, ready, denied, empty, offline, timeout, cancellation, background/resume, and teardown paths.

  6. 06

    Pin dependency and native artifact integrity evidence; retain source fingerprint, selected version, lockfile, build provenance, and approving owner.

  7. 07

    For stateful or hybrid behavior, persist application state outside the SDK and prove idempotency, reconciliation, audit, privacy, and recovery.

  8. 08

    Release by a bounded cohort with observable rollback; repository activity or a successful fixture is never production compatibility evidence.

Private correspondence

Local repository candidates

Only minimized identity evidence is exposed. Review candidates side by side; do not assume they are the same release line.

mapmyindia-intouch-react-native-sdkcontenthub/dochub/mapmyindia-intouch-react-native-sdklocal-contenthub-dochub-mapmyindia-intouch-react-native-sdk