react-native-webrtc / react-native-callkeep

iOS CallKit framework and Android ConnectionService for React Native

ISC License

925 stars 445 forks source link

com.facebook.react.internal.turbomodule.core.TurboModuleInteropUtils$ParsingException: Unable to parse @ReactMethod annotations from native module: RNCallKeep. Details: Module exports two methods to JavaScript with the same name: "displayIncomingCall #798

Open kmamtora opened 4 months ago

kmamtora commented 4 months ago

Bug report

[ ] I've checked the example to reproduce the issue.

Error: Exception in HostObject::get for prop 'RNCallKeep': com.facebook.react.internal.turbomodule.core.TurboModuleInteropUtils$ParsingException: Unable to parse @ReactMethod annotations from native module: RNCallKeep. Details: Module exports two methods to JavaScript with the same name: "displayIncomingCall

Reproduced on:
- [x] Android
- [ ] iOS

Description

Steps to Reproduce

Versions

- Callkeep:
- React Native:
- iOS:
- Android:
- Phone model:

Logs

Paste here

AsadAlihp commented 2 months ago

having the same issue

super-potion commented 3 weeks ago

Same issue on latest "react-native": "^0.76.1", but not "react-native": "^0.75.4",

shahzaib803 commented 3 weeks ago

having the same issue

C0rren commented 3 weeks ago

Same issue. RN 0.76.1. newArch enabled.

dan-avg commented 3 weeks ago

Same issue. It happens only on Android when "new arch" is enabled.

To reproduce:

create a new React Native repo
make sure "new arch" is enabled newArchEnabled=true in gradle.properties
install CallKeep and import CallKeep in the index.js file import RNCallKeep from 'react-native-callkeep';
App crashes on start and the error message mentioned in the OP is displayed

Removing the CallKeep import gets rid of the error message. Disabling "new arch" gets rid of the error message.

This happens on React Native 0.76 (where new architecture is enabled by default) and also happens in earlier versions if you enable the new architecture manually.

MoamberRaza commented 3 weeks ago

Same issue.

marcosluizfp commented 2 weeks ago

Same issue. RN 0.76.1. newArch enabled.

The issue below describes the problem:

https://github.com/facebook/react-native/issues/45193

Temporarily disabled newArch on gradle.properties as workaround:


# newArchEnabled=true

arungirivasan commented 5 days ago

same issue.

there is one more issue.

com.facebook.react.internal.turbomodule.core.TurboModuleInteropUtils$ParsingException: Unable to parse @ReactMethod annotations from native module: RNCallKeep. Details: Module exports two methods to JavaScript with the same name: "startCall

TSk198 commented 4 days ago

i think RN Callkeep dose not support New Arch yet. Check here