expo: [bare] 'UMCore/UMModuleRegistry.h' file not found after upgrading expo-* dependencies to 8.0.0
π Bug Report
After upgrading the expo dependencies to the latest versions I get this build error in Xcode:
'UMCore/UMModuleRegistry.h' file not found
The error happens here https://github.com/expo/expo/blob/1104a04265b8956d5f5e3c557039561ae58b2bd1/packages/unimodules-permissions-interface/ios/UMPermissionsInterface/UMPermissionsInterface.h#L4
Environment
Expo CLI 3.11.1 environment info: System: OS: macOS 10.15.1 Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.11.1 - ~/.nvm/versions/node/v12.11.1/bin/node Yarn: 1.19.1 - /usr/local/bin/yarn npm: 6.11.3 - ~/.nvm/versions/node/v12.11.1/bin/npm Watchman: 4.9.4 - /usr/local/bin/watchman IDEs: Android Studio: 3.5 AI-191.8026.42.35.5900203 Xcode: 11.2.1/11B53 - /usr/bin/xcodebuild npmPackages: react: 16.9.0 => 16.9.0 react-native: 0.61.5 => 0.61.5 react-navigation: 4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 3.11.1
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 8
- Comments: 21 (14 by maintainers)
Commits related to this issue
- [expo] Add missing dependencies (#6503) Why Resolves #6477. When the user in bare-flow use use_frameworks! in his Podfile, the project won't compile. It happens because of missing dependencies i... — committed to expo/expo by lukmccall 5 years ago
- [expo] Add missing dependencies (#6503) Why Resolves #6477. When the user in bare-flow use use_frameworks! in his Podfile, the project won't compile. It happens because of missing dependencies i... — committed to Jamedjo/expo by lukmccall 5 years ago
can you try reinstalling pods?
Iβm not sure whether this fix is released or not. Here is my work-around - just adding this hooking code to Podfile. It works for me.
I found a PR for a similar error here: https://github.com/bamlab/react-native-image-resizer/pull/211 and made a similar patch for
@unimodules/react-native-adapter:@lukmccall does that look right to you? Project seems to build and run without errors now.
I ran
rm -rf Pods && rm -rf Podfile.lock && pod installand then cleaned the project in Xcode, deleted Derived Data and restarted Xcode. Still get the same error though. Before auto-linking was around, I could often fix errors like this in Xcode by fixing the Header Search Paths.Just in case, here is the contents of my Podfile.lock:
Hey amazing job guys this helped me a lot into getting my app to compile!
@lukmccall is there any work ongoing already for applying the patch of the PR that you mentioned in your comment to
@unimodules/react-native-adapter/ios/UMReactNativeAdapter/Services/UMReactNativeAdapter.m? I can do a PR otherwise since I still had to apply this patch after using an app ejected from Expo SDK36@brentvatne
Thank you! maybe under this https://docs.expo.io/bare/installing-unimodules/#configuration-for-ios we reorder the sections so their steps, 1. edit Podfile 2. Pod install 3. AppDelegate files etcβ¦
@jwoodmansey @ajw-m - i added some text to suggest that users ensure to save their changes before running pod install: https://github.com/expo/expo/commit/643853fdab8109eeec1aba94e35f79ee860fdc03
@redpandatronicsuk thanks for that! Was experiencing the same issues, but now Iβm up and running with the
UMReactNativeAdapter.mpatch, plus the βUMCoreβ addition tounimodules-permissions-interface(mentioned earlier).that patch, for reference/clarity:
@lukmccall I tried the PR and it seems to work. Similarly I had to add
s.dependency 'UMFileSystemInterface'to the podspec file forexpo-av,s.dependency 'UMPermissionsInterface'toexpo-image-pickerands.dependency 'UMCore'tounimodules-file-system-interface.My project builds again π but I get an error during linking now π¦