[IOS][expo-modules-core] error: exception specification of overriding function is more lax than base version about expo HOT 14 CLOSED

@tsapeta

npm ls expo-modules-core                      
[email protected] 
└─┬ [email protected]
 └── [email protected] overridden

Ah.. the issue was I had a overwrite hidden in my package.json for expo-modules-core. Not sure why/how that happened. Removed the overwrite, reinstalled and it's now working (with Expo SDK 51). Thank you.

from expo.

@thomasflorian yes we solved it upgrading to latest expo 51 and ensuring you have in your Podfile:

linkage = ENV['USE_FRAMEWORKS']
if linkage != nil
  Pod::UI.puts "Configuring Pod with #{linkage}ally linked Frameworks".green
  use_frameworks! :linkage => linkage.to_sym
end

Hope that helps you!

from expo.

Same here +1

from expo.

same issue

from expo.

Hello! This is a result of one of many breaking changes introduced in 0.74. Generally, Expo SDK 50 is not meant to be used with this version of React Native. We released SDK 51 just today, which officially supports React Native 0.74 and its bridgeless mode in the new architecture. I really recommend to upgrade to this new SDK 😉

If it's not yet feasible in your project to upgrade the SDK, the workaround for this specific error would be to patch-package this line by adding noexcept keyword, i.e.

- void invokeAsync(std::function<void()> &&func) override {
+ void invokeAsync(std::function<void()> &&func) noexcept override {

However, I can't guarantee that everything else will work properly with RN 0.74.

from expo.

I get the same error while using SDK 51 with the following package.json. So it does not seem to be resolved with the new SDK. I removed node modules and reinstalled (with bun):

    "@expo/vector-icons": "^14.0.0",
    "@hookform/resolvers": "^3.3.4",
    "@react-navigation/native": "^6.1.7",
    "@tanstack/react-query": "^5.29.2",
    "axios": "^1.6.8",
    "expo": "^51.0.0",
    "expo-constants": "~16.0.1",
    "expo-device": "~6.0.2",
    "expo-image-picker": "~15.0.4",
    "expo-linking": "~6.3.1",
    "expo-localization": "~15.0.3",
    "expo-notifications": "~0.28.1",
    "expo-router": "~3.5.9",
    "expo-splash-screen": "~0.27.4",
    "expo-status-bar": "~1.12.1",
    "expo-system-ui": "~3.0.4",
    "expo-web-browser": "~13.0.3",
    "i18next": "^23.7.20",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-hook-form": "^7.51.3",
    "react-i18next": "^14.0.1",
    "react-native": "0.74.1",
    "react-native-gesture-handler": "~2.16.1",
    "react-native-mmkv": "^2.12.2",
    "react-native-pager-view": "6.3.0",
    "react-native-reanimated": "3.10.0",
    "react-native-safe-area-context": "^4.8.2",
    "react-native-screens": "3.31.1",
    "react-native-unistyles": "^2.1.1",
    "react-native-web": "~0.19.10",
    "zod": "^3.22.5",
    "zod-i18n-map": "^2.27.0",
    "zustand": "^4.5.2"

from expo.

@JessedeJonge Could you check which version of expo-modules-core gets installed in your project? You can do this with npm ls expo-modules-core or yarn why expo-modules-core.

from expo.

Same for me, issue were resolved with upgrade of SDK. Thanks

from expo.

We tried upgrading to SDK 51, but on pod install getting:

The Swift pod `ExpoModulesCore` depends upon `React-jsinspector`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

We do not use use_modular_headers! globally, what is best way to solve this?

from expo.

We tried upgrading to SDK 51, but on pod install getting:

The Swift pod `ExpoModulesCore` depends upon `React-jsinspector`, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.

We do not use use_modular_headers! globally, what is best way to solve this?

you can try to add sth like this in your Podfile inside your common_pods or directly in target

pod 'React-RCTText', :path => '../node_modules/react-native/Libraries/Text', :modular_headers => true

from expo.

@marelix2 thanks for that, it helped setting:

pod 'React-jsinspector', :path => '../node_modules/react-native/ReactCommon/jsinspector-modern', :modular_headers => true

But I'm having problems with RCT-Folly now:

The Swift pod ExpoModulesCore depends upon RCT-Folly, which does not define modules. To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries), you may set use_modular_headers! globally in your Podfile, or specify :modular_headers => true for particular dependencies.

Setting the paths don't help:

pod 'RCT-Folly', :path => '../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec', :modular_headers => true

Getting error:

There are multiple dependencies with different sources for RCT-Folly in Podfile:

• RCT-Folly
• RCT-Folly (from ../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec)
• RCT-Folly/Fabric (from ../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec)

from expo.

@aureosouza No clue what to do. Have you tried to remove Podfile.lock and Pods? It usually helps combined with update dependencies to latest.

from expo.

@marelix2 yep did hard reset on everything, but still the same:

rm -rf package-lock.json && rm -rf node_modules && npm i && rm -rf /ios/Podfile.lock && rm -rf ~/Library/Preferences/com.apple.dt.Xcode.plist && rm -rf ~/Library/Caches/CocoaPods && rm -rf /ios/Pods && rm -rf ~/Library/Developer/Xcode/DerivedData && npx pod-install --repo-update

I might open a new issue on this, but thanks anyway.

from expo.

@aureosouza facing the same issue, did you ever figure it out?

from expo.