React Native 0.69.5

[Fernando Rojo]

Hey @dominicstop! I think the new release from #55 may have broken compatibility with RN 0.69.5. Is that possible? I'm seeing this error from pod install

pod install
Using Expo modules
Auto-generating `.xcode.env.local` with $NODE_BINARY=/Users/fernandorojo/.nvm/versions/node/v16.13.0/bin/node
Auto-linking React Native modules for target `zeegexample`: RNGestureHandler, RNReanimated, RNScreens, react-native-ios-context-menu, react-native-menu, and react-native-safe-area-context
[Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json
Analyzing dependencies
[Codegen] Found FBReactNativeSpec
Fetching podspec for `RCT-Folly` from `../../../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
Fetching podspec for `boost` from `../../../node_modules/react-native/third-party-podspecs/boost.podspec`
[!] CocoaPods could not find compatible versions for pod "React-Core":
  In Podfile:
    React-Codegen (from `build/generated/ios`) was resolved to 0.69.5, which depends on
      React-Core (= 0.69.5)

    React-Core (from `../../../node_modules/react-native/`)

    react-native-ios-context-menu (from `../../../node_modules/react-native-ios-context-menu`) was resolved to 1.14.0, which depends on
      React-Core

Specs satisfying the `React-Core (from `../../../node_modules/react-native/`), React-Core (= 0.69.5), React-Core` dependency were found, but they required a higher minimum deployment target.

Aborting run
An unexpected error was encountered. Please report it as a bug:
CocoaPodsError: Command `pod install` failed.
└─ Cause: pod exited with non-zero code: 1
Ignoring ffi-1.13.1 because its extensions are not built. Try: gem pristine ffi --version 1.13.1
]

[Dominic Go]

afdhgasjhfksd i think it's caused by this line in the library podspec (but i haven't changed this in forever tho)

s.platforms = { :ios => "10.0" }

the project podfile must be using iOS 9 as the min. deployment target, e.g.

platform :ios, '10.0'

Could you try setting it to iOS 10 first, and see what happens? If it works, I'll lower the deployment version for library to iOS 9 in a patch update

[Fernando Rojo]

that seems reasonable. maybe the issue is caused elsewhere then. i’ll keep looking

[Fernando Rojo]

i fixed it by upgrading some expo dependencies! these error messages are pretty useless lol

[Dominic Go]

it's fine, no worries haha ghsjfjkdssdhlkfdkldfg