Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Android: WorkletsPackage class name collision with react-native-worklets on RN 0.83+

Abierto
  • ¿Algo no está bien?
#266 1 comentario 2 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
android, java, kotlin, react-native
Área
build-system, mobile

Línea de trabajo

Start by locating the Android WorkletsPackage declaration and its references, then review the react-native.config.js and MainApplication.kt workaround alongside the generated PackageList.java error. Rename the class and update its references so react-native-worklets-core and react-native-worklets can autolink together on React Native 0.83+ without ambiguous imports.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Description

On React Native 0.83+, react-native-worklets-core fails to compile on Android due to a class name collision with react-native-worklets (Reanimated 4 dependency).

Both packages export a class named WorkletsPackage, causing autolinking to generate ambiguous imports in PackageList.java.

Environment

  • React Native: 0.83.1
  • react-native-worklets-core: 2.0.0-beta.4
  • react-native-worklets: 0.7.2 (peer dependency of Reanimated 4.2.1)
  • react-native-vision-camera: 4.7.3
  • react-native-reanimated: 4.2.1

Error

error: a type with the same simple name is already defined by the single-type-import of WorkletsPackage
import com.margelo.worklets.WorkletsPackage;
                   ^
/android/app/build/generated/rncli/src/main/java/com/facebook/react/PackageList.java:86: error: reference to WorkletsPackage is ambiguous

Root Cause

  • react-native-worklets: com.swmansion.worklets.WorkletsPackage
  • react-native-worklets-core: com.margelo.worklets.WorkletsPackage

RN 0.83's stricter autolinking generates both imports, causing Java compilation failure.

Workaround

Exclude react-native-worklets-core from autolinking and manually register:

react-native.config.js:

module.exports = {
  dependencies: {
    'react-native-worklets-core': {
      platforms: { android: null }
    }
  }
};

MainApplication.kt:

PackageList(this).packages.apply {
  add(com.margelo.worklets.WorkletsPackage())
}

Proposed Fix

Rename the Java class to avoid collision:

  • WorkletsPackage → WorkletsCorePackage

This would align with the package name and prevent conflicts with Software Mansion's react-native-worklets.

Additional Context

  • This only affects RN 0.83+ (confirmed working on RN 0.81.5)
  • Both packages are required (VisionCamera needs worklets-core, Reanimated needs worklets)
  • No JSI/C++ collision — purely Android autolinking issue
  • The two packages coexist fine at the native layer (different C++ namespaces)
Lenguaje dominante
C++
Estrellas
791
Forks
65
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de margelo/react-native-worklets-core

Todos los issues de margelo/react-native-worklets-core

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.