[Bug]: 10.1.40 Android build fails on RN 0.76 due to lifecycle compatibility issues in v26 LifecycleCompat.kt

[fractalscape13]

Mapbox Implementation

Mapbox

Mapbox Version

10.19.0

React Native Version

0.76.9

Platform

Android

@rnmapbox/maps version

10.1.40

Standalone component to reproduce

import React from 'react';
import {
  MapView,
  ShapeSource,
  LineLayer,
  Camera,
} from '@rnmapbox/maps';

const aLine = {
  type: 'LineString',
  coordinates: [
    [-74.00597, 40.71427],
    [-74.00697, 40.71527],
  ],
};

class BugReportExample extends React.Component {
  render() {
    return (
      <MapView style={{flex: 1}}>
        <Camera centerCoordinate={[-74.00597, 40.71427]} zoomLevel={14} />
        <ShapeSource id="idStreetLayer" shape={aLine}>
          <LineLayer id="idStreetLayer" />
        </ShapeSource>
      </MapView>
    );
  }
}

Observed behavior and steps to reproduce

The v26 LifecycleCompat file uses newer lifecycle APIs not available in RN 0.76

Error: Unresolved reference: setViewTreeLifecycleOwner

The fix is to use the older ViewTreeLifecycleOwner.set() API and getLifecycle() method

Expected behavior

No response

Notes / preliminary analysis

Able to build Android with this patch

@rnmapbox+maps+10.1.40.patch

Additional links and references

No response

[mfazekas]

@fractalscape13 looks good to me, can you please open a PR?

[mfazekas]

Issue Reproduced! ✅

I've successfully reproduced the issue. The problem occurs only when targetSdkVersion is set to 35. React Native 0.76.9 defaults to targetSdkVersion 34, which is why the issue doesn't occur with default settings.

Root Cause Analysis

The issue is related to how @rnmapbox/maps handles lifecycle compatibility between different Android SDK versions:

1. targetSdkVersion 34 or below: Uses the older lifecycle API (ViewTreeLifecycleOwner.set() and getLifecycle() method)
2. targetSdkVersion 35: Attempts to use newer lifecycle API (setViewTreeLifecycleOwner extension function and lifecycle property)

The problem: React Native 0.76.9 doesn't include the androidx.lifecycle version that supports the setViewTreeLifecycleOwner extension function, causing the compilation error.

Reproduction Steps

# 1. Create a new React Native project
npx @react-native-community/cli@latest init TestMapbox3909 --version 0.76.9

# 2. Install @rnmapbox/maps
cd TestMapbox3909
yarn add @rnmapbox/maps@10.1.40

# 3. ⚠️ KEY STEP: Change targetSdkVersion to 35 in android/build.gradle
# Edit android/build.gradle and change:
# targetSdkVersion = 34  -->  targetSdkVersion = 35

# 4. Configure Mapbox repository (add to android/build.gradle after "apply plugin: "com.facebook.react.rootproject"")
allprojects {
    repositories {
        google()
        mavenCentral()
        maven {
            url 'https://api.mapbox.com/downloads/v2/releases/maven'
            authentication {
                basic(BasicAuthentication)
            }
            credentials {
                username = 'mapbox'
                password = project.properties['MAPBOX_DOWNLOADS_TOKEN'] ?: ""
            }
        }
    }
}

# 5. Build Android
cd android
./gradlew assembleDebug

Build Results

With targetSdkVersion = 34 (React Native 0.76.9 default)

✅ BUILD SUCCESSFUL - No errors

With targetSdkVersion = 35

❌ BUILD FAILED with the exact error reported:

e: .../LifecycleCompat.kt:8:27 Unresolved reference: setViewTreeLifecycleOwner
e: .../LifecycleCompat.kt:42:18 Unresolved reference: setViewTreeLifecycleOwner

Temporary Workaround

Until this is fixed, users encountering this issue should:

1. Keep targetSdkVersion = 34 (the React Native 0.76.9 default)
2. Or wait for a fix that properly handles lifecycle compatibility

Proposed Fix

The lifecycle compatibility layer in @rnmapbox/maps needs to be updated to handle React Native 0.76.9's lifecycle version when targetSdkVersion is 35. The src/main/lifecycle-compat/v26/ implementation should use the same API as v25 until React Native updates its androidx.lifecycle dependency.

@SteffeyDev The issue you're experiencing is likely because you've set targetSdkVersion to 35. Can you confirm your targetSdkVersion setting?