feat: expose device-based consent APIs in React Native bridge

[denischilik]

Add device-level consent state to React Native bridge

Summary

Exposes device-level consent APIs in the React Native wrapper so apps can set, read, and clear device-scoped consent from JavaScript. Native device consent (added in mParticle Apple SDK and android-core) supersedes per-user/MPID consent when set — consent collected before login or across identity changes at checkout is retained on the device.

Bridges to:

• iOS — MParticle.sharedInstance().deviceConsentState (requires mParticle Apple SDK 9.2+ with device consent)
• Android — MParticle.getInstance().setDeviceConsentState() / getDeviceConsentState() (requires android-core release with device consent APIs; resolves via [5.79.2, 6.0))

What has changed

• Added setDeviceConsentState, clearDeviceConsentState, and getDeviceConsentState to the JS API and default export
• Wired TurboModule/codegen spec, Android MParticleModule, and iOS RNMParticle (old arch + new arch)
• Reused existing consent map converters on Android; added RCTConvert MPConsentState: and consentStateToDictionary: on iOS

Sample code

import {
  setDeviceConsentState,
  clearDeviceConsentState,
  getDeviceConsentState,
} from 'react-native-mparticle';

// Set device-wide consent (supersedes any per-user consent)
setDeviceConsentState({
  gdpr: {
    data_sharing: {
      consented: true,
      document: 'privacy_policy_v3',
      timestamp: Date.now(),
    },
  },
});

// Clear — reverts to user/MPID-level consent
clearDeviceConsentState();

// Read current device consent
getDeviceConsentState((state) => {
  console.log(state);
});

Testing

• ./gradlew test and ./gradlew ktlintCheck pass on the Android module

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

Related Android PR: mParticle/mparticle-android-sdk#726

Related iOS PR: mParticle/mparticle-apple-sdk#784 (merged)

[cursor]

PR Summary

Medium Risk
Changes affect privacy/consent behavior and how timestamps are parsed for GDPR/CCPA; incorrect mapping could mis-report consent, though scope is limited to new device APIs and existing consent converters.

Overview
Adds device-scoped consent to the public JS API via setDeviceConsentState, clearDeviceConsentState, and getDeviceConsentState, wired through the TurboModule spec and native bridges on Android and iOS (old and new architecture). Device consent maps to MParticle device consent on the native SDKs and can override per-user/MPID consent when set.

Introduces a DeviceConsentState type (GDPR purposes + optional CCPA) and shared conversion helpers: Android builds/reads full ConsentState objects and treats empty payloads as clear; iOS adds RCTConvert MPConsentState: and round-trip consentStateToDictionary: for reads.

Consent timestamp handling is tightened on both platforms—Android accepts number or string millis via readConsentTimestampMillis; iOS GDPR/CCPA converters interpret JS timestamps as epoch milliseconds instead of generic NSDate conversion.

^{Reviewed by Cursor Bugbot for commit ab85cc1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 3 total unresolved issues (including 2 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a30b9e8. Configure here.}