Skip to content
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

[Bug] New Arch support throwing error #368

Open
mobinni opened this issue Nov 12, 2024 · 2 comments
Open

[Bug] New Arch support throwing error #368

mobinni opened this issue Nov 12, 2024 · 2 comments

Comments

@mobinni
Copy link

mobinni commented Nov 12, 2024

Describe the bug
When doing a clean install from scratch with a barebones RN project (non-expo) with new arch enabled the following errors pop up

Screenshot 2024-11-12 at 4 05 32 PM

I also had to disable this in the

//@implementation NativeMMKVStorageSpecBase
//
//
//- (void)setEventEmitterCallback:(EventEmitterCallbackWrapper *)eventEmitterCallbackWrapper
//{
//  _eventEmitterCallback = std::move(eventEmitterCallbackWrapper->_eventEmitterCallback);
//}
//@end
Screenshot 2024-11-12 at 4 08 04 PM

To Reproduce
Steps to reproduce the behavior:

  1. Create a new app
  2. Install 0.11.2
  3. Run ❯ RCT_NEW_ARCH_ENABLED=1 pod install
  4. Build app

Expected behavior
MMKV bindings are installed

Screenshots
If applicable, add screenshots to help explain your problem.

Platform Information:

  • OS: iOS
  • React Native Version 0.75.4
  • Library Version 0.11.2 and 0.11.0
@efstathiosntonas
Copy link

same here with slightly different error on react-native 0.76.2 and [email protected]

xcode console logs:

'JSI bindings were not installed for: MMKVStorage', [TypeError: Cannot read property 'install' of null]
Error: MMKVStorage bindings not installed, js engine: hermes
libc++abi: terminating due to uncaught exception of type std::__1::bad_function_call: std::exception

@mobinni
Copy link
Author

mobinni commented Nov 19, 2024

@efstathiosntonas I was able to resolve this on 0.76+ in terms of the binding not being available I had to make sure to run RCT_NEW_ARCH_ENABLED=1 pod install after a pod deintegrate and clean my build folder and rebuild.

On 0.75 it doesn't seem to be supported at all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants