-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
TypeError: undefined is not an object (evaluating 'InnerNativeModule.installCoreFunctions') #2525
Comments
Issue validatorThe issue is valid! |
Hey @shobhitsinghal624 👋 |
I'm taking a look a reproducing this with a fresh RN app 👍🏻 will report back soon! |
In the meantime here is my
|
Seems ok on a fresh React Native 0.66 app
Wonder if it's an interaction with some other package... only happening for us on iOS though. Is that the case for you as well @shobhitsinghal624 or is it crashing on Android too? |
Sorry I take that back, this does error with the Salesforce SDK-generated app, both on Android and iOS just by importing |
I get this too on Android, since updating to The console log on startup of the app is:
|
@piaskowyk OK so it looks like some changes were made in React Native version 0.58.6 (three years ago!!) that in our case were missing from our @gavrichards and anyone else still seeing this issue, do you follow the upgrade helper every time you upgrade React Native? You can see the changes I mean here in Must be some similar changes on the Android side that we'd already made. |
@mjmasn yes, I follow it to the letter, every time. |
I've figured it out - there are some steps in the installation docs that must not have been there when I initially installed this package. |
Hi guys, anyone got this fixed ? |
I have followed all the steps, but things are still not working. It works on Android, but doesn;t work on iOS. What am I missing? info Fetching system and libraries information...
System:
OS: macOS 11.4
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 920.34 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.3.0 - /var/folders/y_/gy00qtms2kq6v3380xs2k1cm0000gq/T/yarn--1636477167680-0.13777315466882145/node
Yarn: 1.22.11 - /var/folders/y_/gy00qtms2kq6v3380xs2k1cm0000gq/T/yarn--1636477167680-0.13777315466882145/yarn
npm: 7.15.1 - ~/.nvm/versions/node/v16.3.0/bin/npm
Watchman: 2021.08.30.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.0.1, iOS 15.0, macOS 12.0, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3, 31.0.0
System Images: android-25 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.2 AI-202.7660.26.42.7351085
Xcode: 13.1/13A1030d - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.2 => 0.66.2
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found Reanimated version: I keep getting this error: ERROR TypeError: Cannot read property 'installCoreFunctions' of undefined, js engine: hermes
ERROR Error: Requiring module "d11-app/src/components/DummyNotification.tsx", which threw an exception: TypeError: Cannot read property 'installCoreFunctions' of undefined, js engine: hermes I did some digging and
|
I think I figured it out. In my case it worked on Android, but didn't work on iOS. It is now working fine. I followed all the installation steps here - and therefore turned off autoinstall by mistake:
After removing the compilation flag DONT_AUTOINSTALL_REANIMATED again, it worked. Please make sure to re-install your pods and clean your npm cache. Hope that helps! |
I do expereince the same issue, but in my case it fails for App Clip https://developer.apple.com/app-clips/ iOS target. It works for ordinary iOS target. Here is my Pofdile
and react-native info
|
I'm also running into this issue on iOS. Android is working fine. This is after following all the documented install steps.
|
I spent a few hours debugging this and my issue was very specific and might not apply to everyone but as a data point: The issue I ran into was my |
having issue with a project using the brownfield library on ios. we were able to adapt the solution to get it to work on android, but since we dont have a traditional greenfield repo setup is it possible that the script to setup turbo modules not working? |
Running into the same Issue trying to use reanimated within a Swift Framework. |
I temporarily resolved that way downgrade from 2.3.1 to 2.2.4 yarn remove react-native-reanimated
yarn add [email protected] -E and with these installation instructions: https://docs.swmansion.com/react-native-reanimated/docs/2.2.0/installation my environment is like this
|
Thx!!! |
Has anyone got this issue still? |
Yep after I downgraded to 2.2.0, because getting weird bugs on newest version but Expo notifies that I need to update. When I update its ok tho |
@TomasSestak could you provide me a repo to reproduce the issue? It helps me a lot! 🙏 |
@piaskowyk How about this https://codesandbox.io/s/reanimated2playground-83hf7? |
Just follow this guide: Thanks @gavrichards @mjmasn |
To resolve this issue on the web you should update reanimated to 2.3.1 |
The most probable causes of this issue are:
|
If this doesn't help please provide me a repo to reproduce the issue and we will fix it. |
Tried the above, still doesn't work. Trying to setup renanimated2 with swift. Have tried with both (with and without CPP flag). still getting installCoreFunctions is undefined. global.__reanimatedModuleProxy is not getting set. |
#1439 (comment) works for me. |
Worked like a charm for me. Thanks |
We have this issue still on our app. Works fine on iOS until 2.2.0, but upgrading beyond 2.3.0 and this error arrives. We need to have a version which does not require hermes. |
Description
App crashes with this error:
Expected behavior
App should not crash.
Actual behavior & steps to reproduce
NA
Snack or minimal code example
NA
Package versions
Affected platforms
The text was updated successfully, but these errors were encountered: