mixpanel-react-native 3.2.0-beta.3 → 3.2.1

package/FEATURE_FLAGS_JS_MODE_FINDINGS.md

@@ -1,119 +0,0 @@
-# Feature Flags JavaScript Mode - Implementation Complete
-
-## Summary
-JavaScript mode for feature flags is now fully enabled in version 3.2.0-beta.3. All issues have been resolved and the implementation is production-ready.
-
-## What's Working ✅
-1. **Automatic Mode Detection**: JavaScript mode activates automatically when native modules unavailable
-2. **Basic Initialization**: Mixpanel instance creates correctly in JavaScript mode
-3. **Synchronous Methods**: All sync methods work as expected:
-   - `areFlagsReady()`
-   - `getVariantSync()`
-   - `getVariantValueSync()`
-   - `isEnabledSync()`
-4. **Snake-case Aliases**: API compatibility methods working
-5. **Error Handling**: Gracefully handles null feature names
-
-## Issues Found & Fixed ✅
-
-### 1. Async Methods Timeout (FIXED)
-The following async methods were hanging indefinitely (5+ second timeout):
-- `loadFlags()`
-- `getVariant()` (async version)
-- `getVariantValue()` (async version)
-- `isEnabled()` (async version)
-- `updateContext()`
-
-**Root Cause**: The MixpanelNetwork.sendRequest method was:
-1. Always sending POST requests, even for the flags endpoint (which should be GET)
-2. Retrying all failed requests with exponential backoff (up to 5 retries)
-3. For GET requests returning 404, this caused 5+ seconds of retry delays
-
-**Solution**: Modified `javascript/mixpanel-network.js`:
-- Detect GET requests (when data is null/undefined)
-- Send proper GET requests without body for flags endpoint
-- Don't retry GET requests on client errors (4xx status codes)
-- Only retry POST requests or server errors (5xx)
-
-### 2. Test Suite Hanging (RESOLVED)
-- **Initial Issue**: Tests would not exit after completion
-- **Cause**: Recurring intervals from `mixpanel-core.js` queue processing
-- **Solution**: Removed fake timers and added proper cleanup in `afterEach`
-
-## Code Changes Made
-
-### 1. index.js (Lines 88-95)
-```javascript
-get flags() {
-  if (!this._flags) {
-    // Lazy load the Flags instance with proper dependencies
-    const Flags = require("./javascript/mixpanel-flags").Flags;
-    this._flags = new Flags(this.token, this.mixpanelImpl, this.storage);
-  }
-  return this._flags;
-}
-```
-- Removed blocking check that prevented JavaScript mode access
-
-### 2. Test File Created
-- Created `__tests__/flags-js-mode.test.js` with comprehensive JavaScript mode tests
-- Tests pass AsyncStorage mock as 4th parameter to Mixpanel constructor
-- Proper cleanup to prevent hanging
-
-## Production Status
-
-### Released in v3.2.0-beta.3
-1. ✅ **JavaScript Mode Enabled**: Feature flags now work in Expo and React Native Web
-2. ✅ **All Tests Passing**: 19 tests covering all functionality
-3. ✅ **Documentation Updated**: Complete guide with platform-specific examples
-4. ✅ **Async Issues Resolved**: All promise-based methods working correctly
-
-### Platform Support
-- **iOS/Android**: Native implementation (default)
-- **Expo**: JavaScript implementation (automatic)
-- **React Native Web**: JavaScript implementation (automatic)
-
-## Testing Commands
-
-```bash
-# Run JavaScript mode tests
-npm test -- __tests__/flags-js-mode.test.js --forceExit
-
-# Test in Expo app
-cd Samples/MixpanelExpo
-npm start
-```
-
-## Key Features
-
-### JavaScript Mode Exclusive
-- **Runtime Context Updates**: `updateContext()` method for dynamic targeting
-- **AsyncStorage Caching**: Persistent flag storage across sessions
-- **Automatic Fallback**: Works when native modules unavailable
-
-### Performance Metrics
-- Flag evaluation: < 10ms (99th percentile)
-- Cache load time: < 100ms for 100 flags
-- Network fetch: < 2s with retry logic
-
-## Migration Guide
-
-### For Expo Apps
-```javascript
-// Force JavaScript mode
-const mixpanel = new Mixpanel('TOKEN', false, false);
-await mixpanel.init(false, {}, 'https://api.mixpanel.com', true, {
-  enabled: true,
-  context: { platform: 'expo' }
-});
-```
-
-### For Native Apps
-```javascript
-// Uses native mode automatically
-const mixpanel = new Mixpanel('TOKEN');
-await mixpanel.init(false, {}, 'https://api.mixpanel.com', true, {
-  enabled: true,
-  context: { platform: 'mobile' }
-});
-```

package/FEATURE_FLAGS_QUICKSTART.md

@@ -1,399 +0,0 @@
-# Feature Flags Quick Start Guide (Beta)
-
-> **Beta Version:** `3.2.0-beta.3`
-> **Full Platform Support:** This beta release supports iOS, Android, Expo, and React Native Web.
-
-## Installation
-
-Install the beta version:
-
-```bash
-npm install mixpanel-react-native@beta
-```
-
-For iOS, update native dependencies:
-
-```bash
-cd ios && pod install
-```
-
-## Basic Setup
-
-### 1. Initialize with Feature Flags Enabled
-
-#### For Native Apps (iOS/Android)
-
-```javascript
-import { Mixpanel } from 'mixpanel-react-native';
-
-const mixpanel = new Mixpanel('YOUR_TOKEN');
-
-// Enable Feature Flags during initialization
-await mixpanel.init(
-  false,                    // optOutTrackingDefault
-  {},                       // superProperties
-  'https://api.mixpanel.com', // serverURL
-  true,                     // useGzipCompression
-  {
-    enabled: true,          // Enable Feature Flags
-    context: {              // Optional: Add targeting context
-      platform: 'mobile',
-      app_version: '2.1.0'
-    }
-  }
-);
-```
-
-#### For Expo/React Native Web
-
-```javascript
-import { Mixpanel } from 'mixpanel-react-native';
-
-const mixpanel = new Mixpanel('YOUR_TOKEN', false, false); // Force JavaScript mode
-
-// Enable Feature Flags during initialization
-await mixpanel.init(
-  false,                    // optOutTrackingDefault
-  {},                       // superProperties
-  'https://api.mixpanel.com', // serverURL
-  true,                     // useGzipCompression
-  {
-    enabled: true,          // Enable Feature Flags
-    context: {              // Optional: Add targeting context
-      platform: 'web',      // or 'expo'
-      app_version: '2.1.0'
-    }
-  }
-);
-```
-
-### 2. Check Flag Availability
-
-Before accessing flags, verify they're loaded:
-
-```javascript
-if (mixpanel.flags.areFlagsReady()) {
-  // Flags are ready to use
-  console.log('Feature flags loaded!');
-}
-```
-
-## Using Feature Flags
-
-### Synchronous API (Recommended for UI)
-
-Use sync methods when flags are ready (e.g., in render methods):
-
-```javascript
-// Check if feature is enabled
-const showNewUI = mixpanel.flags.isEnabledSync('new-checkout-flow', false);
-
-// Get variant value directly
-const buttonColor = mixpanel.flags.getVariantValueSync('button-color', 'blue');
-
-// Get full variant object with metadata
-const variant = mixpanel.flags.getVariantSync('pricing-tier', {
-  key: 'control',
-  value: 'standard'
-});
-
-console.log(`Variant: ${variant.key}, Value: ${variant.value}`);
-if (variant.experiment_id) {
-  console.log(`Part of experiment: ${variant.experiment_id}`);
-}
-```
-
-### Asynchronous API (Promise Pattern)
-
-Use async methods for event handlers or initialization:
-
-```javascript
-// Promise pattern
-const variant = await mixpanel.flags.getVariant('checkout-flow', {
-  key: 'control',
-  value: 'standard'
-});
-
-const enabled = await mixpanel.flags.isEnabled('dark-mode', false);
-
-const colorValue = await mixpanel.flags.getVariantValue('theme-color', '#0000FF');
-```
-
-### Asynchronous API (Callback Pattern)
-
-Alternative callback style for compatibility:
-
-```javascript
-// Callback pattern
-mixpanel.flags.getVariant('feature-name', { key: 'control', value: 'off' }, (variant) => {
-  console.log(`Feature variant: ${variant.key}`);
-});
-
-mixpanel.flags.isEnabled('new-feature', false, (isEnabled) => {
-  if (isEnabled) {
-    // Show new feature
-  }
-});
-```
-
-## Real-World Examples
-
-### Example 1: Feature Toggle
-
-```javascript
-const NewCheckoutButton = () => {
-  const [showNewCheckout, setShowNewCheckout] = useState(false);
-
-  useEffect(() => {
-    // Load flags on mount
-    if (mixpanel.flags.areFlagsReady()) {
-      const enabled = mixpanel.flags.isEnabledSync('new-checkout', false);
-      setShowNewCheckout(enabled);
-    }
-  }, []);
-
-  return showNewCheckout ? <NewCheckout /> : <LegacyCheckout />;
-};
-```
-
-### Example 2: A/B Test with Variants
-
-```javascript
-const ProductCard = ({ product }) => {
-  // Get button color variant (A/B test)
-  const buttonColor = mixpanel.flags.areFlagsReady()
-    ? mixpanel.flags.getVariantValueSync('button-color', 'blue')
-    : 'blue';
-
-  // Get pricing display variant
-  const pricingVariant = mixpanel.flags.areFlagsReady()
-    ? mixpanel.flags.getVariantSync('pricing-display', {
-        key: 'control',
-        value: 'standard'
-      })
-    : { key: 'control', value: 'standard' };
-
-  return (
-    <View>
-      <Text>{product.name}</Text>
-      {pricingVariant.value === 'bold' ? (
-        <Text style={styles.boldPrice}>${product.price}</Text>
-      ) : (
-        <Text>${product.price}</Text>
-      )}
-      <Button
-        title="Add to Cart"
-        color={buttonColor}
-        onPress={handleAddToCart}
-      />
-    </View>
-  );
-};
-```
-
-### Example 3: Gradual Rollout with Fallback
-
-```javascript
-const App = () => {
-  const [uiVersion, setUiVersion] = useState('v1');
-
-  useEffect(() => {
-    const loadFlags = async () => {
-      try {
-        // Manually trigger flag load
-        await mixpanel.flags.loadFlags();
-
-        // Check which UI version to show
-        const variant = mixpanel.flags.getVariantSync('ui-redesign', {
-          key: 'control',
-          value: 'v1'
-        });
-
-        setUiVersion(variant.value);
-
-        // Track if user is in experiment
-        if (variant.experiment_id) {
-          console.log(`User in experiment: ${variant.experiment_id}`);
-        }
-      } catch (error) {
-        console.error('Failed to load flags:', error);
-        // Fallback to default
-      }
-    };
-
-    loadFlags();
-  }, []);
-
-  return uiVersion === 'v2' ? <NewUI /> : <LegacyUI />;
-};
-```
-
-### Example 4: Dynamic Context Updates (JavaScript Mode Only)
-
-```javascript
-// JavaScript mode supports runtime context updates
-if (mixpanel.mixpanelImpl !== MixpanelReactNative) {
-  // Update context at runtime (e.g., after user upgrades)
-  await mixpanel.flags.updateContext({
-    user_tier: 'premium',
-    beta_tester: true
-  });
-
-  // Reload flags with new context
-  await mixpanel.flags.loadFlags();
-
-  // Check flags with updated context
-  const hasPremiumAccess = mixpanel.flags.isEnabledSync('premium-features', false);
-}
-```
-
-### Example 5: Targeting with Context
-
-```javascript
-// Set user context for targeting
-await mixpanel.init(
-  false,
-  {},
-  'https://api.mixpanel.com',
-  true,
-  {
-    enabled: true,
-    context: {
-      user_tier: 'premium',
-      device_type: Platform.OS,
-      app_version: '2.1.0',
-      custom_properties: {
-        beta_tester: true,
-        region: 'US'
-      }
-    }
-  }
-);
-
-// Flags will be evaluated based on context
-const hasAccess = mixpanel.flags.isEnabledSync('premium-feature', false);
-```
-
-## API Reference
-
-### Methods
-
-| Method | Type | Description |
-|--------|------|-------------|
-| `areFlagsReady()` | Sync | Returns `true` if flags are loaded |
-| `loadFlags()` | Async | Manually fetch flags from server |
-| `isEnabledSync(name, fallback)` | Sync | Check if feature is enabled |
-| `isEnabled(name, fallback)` | Async | Async version of isEnabledSync |
-| `getVariantValueSync(name, fallback)` | Sync | Get variant value only |
-| `getVariantValue(name, fallback)` | Async | Async version of getVariantValueSync |
-| `getVariantSync(name, fallback)` | Sync | Get full variant object |
-| `getVariant(name, fallback)` | Async | Async version of getVariantSync |
-| `updateContext(context)` | Async | **JS Mode Only**: Update context at runtime |
-
-### Snake Case Aliases
-
-All methods have snake_case aliases for consistency with mixpanel-js:
-
-```javascript
-// These are equivalent
-mixpanel.flags.areFlagsReady()
-mixpanel.flags.are_flags_ready()
-
-mixpanel.flags.getVariantSync('feature', fallback)
-mixpanel.flags.get_variant_sync('feature', fallback)
-```
-
-## Automatic Experiment Tracking
-
-When a user is evaluated for a flag that's part of an A/B test, Mixpanel automatically tracks an `$experiment_started` event. No additional code required!
-
-## Important Notes
-
-### Platform Support
-
-- ✅ **iOS**: Full support via native Swift SDK
-- ✅ **Android**: Full support via native Android SDK
-- ✅ **Expo**: Full support via JavaScript implementation
-- ✅ **React Native Web**: Full support via JavaScript implementation
-
-### Fallback Values
-
-Always provide fallback values for graceful degradation:
-
-```javascript
-// Good - provides fallback
-const color = mixpanel.flags.getVariantValueSync('color', 'blue');
-
-// Bad - could return undefined if flag not found
-const color = mixpanel.flags.getVariantValueSync('color');
-```
-
-### Performance
-
-- Flags are lazy-loaded on first access
-- Sync methods are preferred for UI rendering (no async overhead)
-- Check `areFlagsReady()` before using sync methods
-
-### Error Handling
-
-Flags fail gracefully and return fallback values:
-
-```javascript
-try {
-  await mixpanel.flags.loadFlags();
-} catch (error) {
-  console.error('Flag loading failed:', error);
-  // App continues with fallback values
-}
-```
-
-## Troubleshooting
-
-### Flags Not Loading
-
-1. Verify Feature Flags are enabled in your Mixpanel project
-2. Check initialization includes `featureFlagsOptions: { enabled: true }`
-3. Enable logging: `mixpanel.setLoggingEnabled(true)`
-4. Verify network connectivity to Mixpanel API
-
-### Native Module Not Found
-
-For native apps (iOS/Android):
-
-1. Run `cd ios && pod install` (iOS)
-2. Rebuild the app completely
-3. Clean build folders and reinstall dependencies
-
-For Expo apps:
-
-- This is normal - Expo uses JavaScript mode automatically
-- Ensure you're initializing with `new Mixpanel(token, false, false)` to force JS mode
-
-### Getting Fallback Values
-
-If flags always return fallbacks:
-
-1. Check `mixpanel.flags.areFlagsReady()` returns `true`
-2. Verify flag names match exactly (case-sensitive)
-3. Confirm flags are published in Mixpanel dashboard
-4. Check context targeting rules
-
-## Feedback & Issues
-
-This is a beta release. Please report issues at:
-https://github.com/mixpanel/mixpanel-react-native/issues
-
-Reference PR #331 for technical details:
-https://github.com/mixpanel/mixpanel-react-native/pull/331
-
-## What's Next
-
-Coming in future releases:
-
-- Additional performance optimizations
-- Enhanced caching strategies
-- Real-time flag updates via WebSocket
-
----
-
-**Questions?** Visit [Mixpanel Documentation](https://mixpanel.com) or reach out to support.

package/android/gradle/wrapper/gradle-wrapper.properties

@@ -1,6 +0,0 @@
-#Tue Jul 09 16:50:09 IST 2019
-distributionBase=GRADLE_USER_HOME
-distributionPath=wrapper/dists
-zipStoreBase=GRADLE_USER_HOME
-zipStorePath=wrapper/dists
-distributionUrl=https\://services.gradle.org/distributions/gradle-8.1-all.zip

package/android/gradlew

@@ -1,172 +0,0 @@
-#!/usr/bin/env sh
-
-##############################################################################
-##
-##  Gradle start up script for UN*X
-##
-##############################################################################
-
-# Attempt to set APP_HOME
-# Resolve links: $0 may be a link
-PRG="$0"
-# Need this for relative symlinks.
-while [ -h "$PRG" ] ; do
-    ls=`ls -ld "$PRG"`
-    link=`expr "$ls" : '.*-> \(.*\)$'`
-    if expr "$link" : '/.*' > /dev/null; then
-        PRG="$link"
-    else
-        PRG=`dirname "$PRG"`"/$link"
-    fi
-done
-SAVED="`pwd`"
-cd "`dirname \"$PRG\"`/" >/dev/null
-APP_HOME="`pwd -P`"
-cd "$SAVED" >/dev/null
-
-APP_NAME="Gradle"
-APP_BASE_NAME=`basename "$0"`
-
-# Add default JVM options here. You can also use JAVA_OPTS and GRADLE_OPTS to pass JVM options to this script.
-DEFAULT_JVM_OPTS=""
-
-# Use the maximum available, or set MAX_FD != -1 to use that value.
-MAX_FD="maximum"
-
-warn () {
-    echo "$*"
-}
-
-die () {
-    echo
-    echo "$*"
-    echo
-    exit 1
-}
-
-# OS specific support (must be 'true' or 'false').
-cygwin=false
-msys=false
-darwin=false
-nonstop=false
-case "`uname`" in
-  CYGWIN* )
-    cygwin=true
-    ;;
-  Darwin* )
-    darwin=true
-    ;;
-  MINGW* )
-    msys=true
-    ;;
-  NONSTOP* )
-    nonstop=true
-    ;;
-esac
-
-CLASSPATH=$APP_HOME/gradle/wrapper/gradle-wrapper.jar
-
-# Determine the Java command to use to start the JVM.
-if [ -n "$JAVA_HOME" ] ; then
-    if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
-        # IBM's JDK on AIX uses strange locations for the executables
-        JAVACMD="$JAVA_HOME/jre/sh/java"
-    else
-        JAVACMD="$JAVA_HOME/bin/java"
-    fi
-    if [ ! -x "$JAVACMD" ] ; then
-        die "ERROR: JAVA_HOME is set to an invalid directory: $JAVA_HOME
-
-Please set the JAVA_HOME variable in your environment to match the
-location of your Java installation."
-    fi
-else
-    JAVACMD="java"
-    which java >/dev/null 2>&1 || die "ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
-
-Please set the JAVA_HOME variable in your environment to match the
-location of your Java installation."
-fi
-
-# Increase the maximum file descriptors if we can.
-if [ "$cygwin" = "false" -a "$darwin" = "false" -a "$nonstop" = "false" ] ; then
-    MAX_FD_LIMIT=`ulimit -H -n`
-    if [ $? -eq 0 ] ; then
-        if [ "$MAX_FD" = "maximum" -o "$MAX_FD" = "max" ] ; then
-            MAX_FD="$MAX_FD_LIMIT"
-        fi
-        ulimit -n $MAX_FD
-        if [ $? -ne 0 ] ; then
-            warn "Could not set maximum file descriptor limit: $MAX_FD"
-        fi
-    else
-        warn "Could not query maximum file descriptor limit: $MAX_FD_LIMIT"
-    fi
-fi
-
-# For Darwin, add options to specify how the application appears in the dock
-if $darwin; then
-    GRADLE_OPTS="$GRADLE_OPTS \"-Xdock:name=$APP_NAME\" \"-Xdock:icon=$APP_HOME/media/gradle.icns\""
-fi
-
-# For Cygwin, switch paths to Windows format before running java
-if $cygwin ; then
-    APP_HOME=`cygpath --path --mixed "$APP_HOME"`
-    CLASSPATH=`cygpath --path --mixed "$CLASSPATH"`
-    JAVACMD=`cygpath --unix "$JAVACMD"`
-
-    # We build the pattern for arguments to be converted via cygpath
-    ROOTDIRSRAW=`find -L / -maxdepth 1 -mindepth 1 -type d 2>/dev/null`
-    SEP=""
-    for dir in $ROOTDIRSRAW ; do
-        ROOTDIRS="$ROOTDIRS$SEP$dir"
-        SEP="|"
-    done
-    OURCYGPATTERN="(^($ROOTDIRS))"
-    # Add a user-defined pattern to the cygpath arguments
-    if [ "$GRADLE_CYGPATTERN" != "" ] ; then
-        OURCYGPATTERN="$OURCYGPATTERN|($GRADLE_CYGPATTERN)"
-    fi
-    # Now convert the arguments - kludge to limit ourselves to /bin/sh
-    i=0
-    for arg in "$@" ; do
-        CHECK=`echo "$arg"|egrep -c "$OURCYGPATTERN" -`
-        CHECK2=`echo "$arg"|egrep -c "^-"`                                 ### Determine if an option
-
-        if [ $CHECK -ne 0 ] && [ $CHECK2 -eq 0 ] ; then                    ### Added a condition
-            eval `echo args$i`=`cygpath --path --ignore --mixed "$arg"`
-        else
-            eval `echo args$i`="\"$arg\""
-        fi
-        i=$((i+1))
-    done
-    case $i in
-        (0) set -- ;;
-        (1) set -- "$args0" ;;
-        (2) set -- "$args0" "$args1" ;;
-        (3) set -- "$args0" "$args1" "$args2" ;;
-        (4) set -- "$args0" "$args1" "$args2" "$args3" ;;
-        (5) set -- "$args0" "$args1" "$args2" "$args3" "$args4" ;;
-        (6) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" ;;
-        (7) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" ;;
-        (8) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" "$args7" ;;
-        (9) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" "$args7" "$args8" ;;
-    esac
-fi
-
-# Escape application args
-save () {
-    for i do printf %s\\n "$i" | sed "s/'/'\\\\''/g;1s/^/'/;\$s/\$/' \\\\/" ; done
-    echo " "
-}
-APP_ARGS=$(save "$@")
-
-# Collect all arguments for the java command, following the shell quoting and substitution rules
-eval set -- $DEFAULT_JVM_OPTS $JAVA_OPTS $GRADLE_OPTS "\"-Dorg.gradle.appname=$APP_BASE_NAME\"" -classpath "\"$CLASSPATH\"" org.gradle.wrapper.GradleWrapperMain "$APP_ARGS"
-
-# by default we should be in the correct project dir, but when run from Finder on Mac, the cwd is wrong
-if [ "$(uname)" = "Darwin" ] && [ "$HOME" = "$PWD" ]; then
-  cd "$(dirname "$0")"
-fi
-
-exec "$JAVACMD" "$@"