Datadog sdk version error

[enisze]

Thanks for taking the time for reporting an issue!

If you are having trouble sending data from the SDK but don't see any error, please reach out first through our support team.

Describe what happened

Building ioS with expo throws this error (android works)

CocoaPods could not find compatible versions for pod "DatadogSDK": [INSTALL_PODS] In Podfile: [INSTALL_PODS] DatadogSDKReactNative (from ../../../node_modules/@datadog/mobile-react-native) was resolved to 1.2.1, which depends on [INSTALL_PODS] DatadogSDK (~> 1.14.0) [INSTALL_PODS] None of your spec sources contain a spec satisfying the dependency: DatadogSDK (~> 1.14.0). [INSTALL_PODS] You have either: [INSTALL_PODS] * out-of-date source repos which you can update with pod repo update or with pod install --repo-update. [INSTALL_PODS] * mistyped the name or version. [INSTALL_PODS] * not added the source repo that hosts the Podspec to your Podfile. [INSTALL_PODS]

Steps to reproduce the issue:

Building ioS with expo (android works)

Describe what you expected:

expected that it works :D

Additional context

• package.json "expo-datadog": "^47.0.0", "@datadog/mobile-react-native": "^1.2.1", "@datadog/mobile-react-navigation": "1.2.1",

I tried deleting node_modules already and reinstaling. Did not work.

[louiszawadzki]

Hi @enisze, thanks for reaching out!

Looking at the stacktrace, it could be possible that you are upgrading the SDK and you had a previous version of the DatadogSDK pod SDK installed. This is an iOS dependency of our SDK, and it needs to be updated by cocoapods when we upgrade the version. If you have a Podfile.lock file committed in your project, running pod update instead of pod install locally should solve the issue. If you are running the build with EAS, try running eas build --clear-cache to remove the cache and trigger a new pod update.

If you are still having issues, could you share the following information:

• if you are building locally or with EAS
• if you have a Podfile.lock file and its content if so
• the output from the commands you tried

Thanks a lot!

[enisze]

Hey @louiszawadzki thank you for your quick reply :) I am using eas (locally). I tried the following command: eas build --profile development-simulator --platform ios --local --clear-cache The profile is the following:

    "base": {
      "node": "16.19.0",
      "yarn": "1.18.0"
    },
    "development": {
      "extends": "base",
      "developmentClient": true,
      "distribution": "internal",
    },
    "development-simulator": {
      "extends": "development",
      "ios": {
        "simulator": true
      }
    }

[enisze]

[INSTALL_PODS] Update this package.json to use a subpath pattern like "./*".
[INSTALL_PODS] Using Expo modules
[INSTALL_PODS] [Expo] Enabling modular headers for pod ExpoModulesCore
[INSTALL_PODS] Auto-generating `.xcode.env.local` with $NODE_BINARY=/Users/enisze/.nvm/versions/node/v16.19.0/bin/node
[INSTALL_PODS] RNFBAnalytics: Using default Firebase/Analytics with Ad Ids. May require App Tracking Transparency. Not allowed for Kids apps.
[INSTALL_PODS] RNFBAnalytics: You may set variable `$RNFirebaseAnalyticsWithoutAdIdSupport=true` in Podfile to use analytics without ad ids.
[INSTALL_PODS] Adding a custom script phase for Pod RNFBApp: [RNFB] Core Configuration
[INSTALL_PODS] Auto-linking React Native modules for target `PropRateDev`: DatadogSDKReactNative, RNAWSCognito, RNCAsyncStorage, RNFBAnalytics, RNFBApp, RNGestureHandler, RNReanimated, RNSVG, RNScreens, customerio-reactnative, lottie-react-native, react-native-maps, react-native-safe-area-context, and react-native-webview
[INSTALL_PODS] [Codegen] Generating ./build/generated/ios/React-Codegen.podspec.json
[INSTALL_PODS] Analyzing dependencies
[INSTALL_PODS] Fetching podspec for `DoubleConversion` from `../../../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
[INSTALL_PODS] [Codegen] Found FBReactNativeSpec
[INSTALL_PODS] /private/var/folders/d4/vs95y56x7_ddxqkybw1l9l1w0000gn/T/eas-build-local-nodejs/db488564-967c-4b4c-b456-e105b801aa85/build/node_modules/react-native/scripts/react_native_pods_utils/script_phases.rb:51: warning: Passing safe_level with the 2nd argument of ERB.new is deprecated. Do not use it, and specify other arguments as keyword arguments.
[INSTALL_PODS] /private/var/folders/d4/vs95y56x7_ddxqkybw1l9l1w0000gn/T/eas-build-local-nodejs/db488564-967c-4b4c-b456-e105b801aa85/build/node_modules/react-native/scripts/react_native_pods_utils/script_phases.rb:51: warning: Passing trim_mode with the 3rd argument of ERB.new is deprecated. Use keyword argument like ERB.new(str, trim_mode: ...) instead.
[INSTALL_PODS] Fetching podspec for `RCT-Folly` from `../../../node_modules/react-native/third-party-podspecs/RCT-Folly.podspec`
[INSTALL_PODS] RNFBAnalytics: Using default Firebase/Analytics with Ad Ids. May require App Tracking Transparency. Not allowed for Kids apps.
[INSTALL_PODS] RNFBAnalytics: You may set variable `$RNFirebaseAnalyticsWithoutAdIdSupport=true` in Podfile to use analytics without ad ids.
[INSTALL_PODS] Fetching podspec for `boost` from `../../../node_modules/react-native/third-party-podspecs/boost.podspec`
[INSTALL_PODS] Fetching podspec for `glog` from `../../../node_modules/react-native/third-party-podspecs/glog.podspec`
[INSTALL_PODS] [!] CocoaPods could not find compatible versions for pod "DatadogSDK":
[INSTALL_PODS]   In Podfile:
[INSTALL_PODS]     DatadogSDKReactNative (from `../../../node_modules/@datadog/mobile-react-native`) was resolved to 1.2.1, which depends on
[INSTALL_PODS]       DatadogSDK (~> 1.14.0)
[INSTALL_PODS] None of your spec sources contain a spec satisfying the dependency: `DatadogSDK (~> 1.14.0)`.
[INSTALL_PODS] You have either:
[INSTALL_PODS]  * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
[INSTALL_PODS]  * mistyped the name or version.
[INSTALL_PODS]  * not added the source repo that hosts the Podspec to your Podfile.
[INSTALL_PODS] 

[enisze]

It works on the expo servers running eas build. So it seems to be a local problem.

[louiszawadzki]

Hi @enisze,

Thanks for providing the additional information! Can you try running pod update from the ios folder of your app? If you don't have an ios folder let us know, and if it didn't fix the issue please attach the output from the commands.

Thanks a lot

[enisze]

Hey @louiszawadzki I do not have an ios folder, I just use plain expo / eas.