Error build for react-native-unimodules@0.13.0 and above when using use_frameworks! in Podfile

Summary

Have been trying to upgrade react-native-unimodules@0.12.0 to 0.13.0 or above but failed to do so.

Compilation return error it says

Undefined symbols for architecture x86_64: “OBJC_CLASS$_UMUtilities”, referenced from: objc-class-ref in EXConstantsService.o “OBJC_CLASS$_UMExportedModule”, referenced from: OBJC_CLASS$_EXConstants in EXConstants.o “OBJC_METACLASS$_UMExportedModule”, referenced from: OBJC_METACLASS$_EXConstants in EXConstants.o “_UMRegisterModule”, referenced from: +[EXConstants load] in EXConstants.o +[EXConstantsService load] in EXConstantsService.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

bare

What platform(s) does this occur on?

iOS

SDK Version (managed workflow only)

No response

Environment

Expo CLI 3.28.0 environment info: System: OS: macOS 11.3 Shell: 5.8 - /bin/zsh Binaries: Node: 14.14.0 - /usr/local/bin/node Yarn: 1.22.10 - /usr/local/bin/yarn npm: 6.14.8 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.1 - /Users/budi_tjendra/.rbenv/shims/pod SDKs: iOS SDK: Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 Android SDK: API Levels: 23, 28, 29, 30 Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 30.0.3 System Images: android-24 | Intel x86 Atom_64, android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom IDEs: Android Studio: 4.1 AI-201.8743.12.41.6953283 Xcode: 12.4/12D4e - /usr/bin/xcodebuild npmPackages: react: 16.11.0 => 16.11.0 react-native: ^0.63.3 => 0.63.4 react-navigation: ^4.3.9 => 4.4.4 npmGlobalPackages: expo-cli: 3.28.0 Expo Workflow: bare

Reproducible demo or steps to reproduce from a blank project

this error occur when use_frameworks! is being used in pod file.

[gri-bchen]

same issue on pod version 1.10.1.

[budiTjendra]

The current merged only resolves for pod 1.9.3. Need someone help to resolve the issue with pod v.1.10.1.