-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
Comments
having the same issue |
Same issue on latest "react-native": "^0.76.1", but not "react-native": "^0.75.4", |
having the same issue |
Same issue. RN 0.76.1. newArch enabled. |
Same issue. It happens only on Android when "new arch" is enabled. To reproduce:
Removing the CallKeep import 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. |
Same issue. |
Same issue. RN 0.76.1. newArch enabled. The issue below describes the problem: Temporarily disabled newArch on gradle.properties as workaround:
|
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 |
i think RN Callkeep dose not support New Arch yet. Check here |
Bug report
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
Description
Steps to Reproduce
Versions
Logs
The text was updated successfully, but these errors were encountered: