analytics-react-native: 'Analytics/SEGAnalytics.h' file not found after updating to 1.3.2

I updated from 1.3.1 to 1.3.2 and my iOS app no longer builds and outputs the following error:

'Analytics/SEGAnalytics.h' file not found

I think it is related to the pod dependency: Analytics (4.1.1).

It works as expected if I revert to 1.3.1 Analytics (4.0.5).

react-native-info:

System:
    OS: macOS 10.15.7
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 1.18 GB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.9.1 - ~/.nvm/versions/node/v12.9.1/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v12.9.1/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v12.9.1/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.1, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.6010548
    Xcode: 12.1/12A7403 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_172 - /usr/bin/javac
    Python: 2.7.15 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.3 => 0.63.3
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Reactions: 9
  • Comments: 18 (4 by maintainers)

Most upvoted comments

@martintreurnicht I tried to patch the package with this but is not working, any idea how I could do it ? 'Segment/SEGAnalytics.h' file not found

Thank you 😻

@DuncanLewis all device mode libraries have been updated to reflect the Segment path being used for the headers. I can’t list them all here, but be sure you do a pod repo update to make sure CocoaPods has all the latest versions available.

Closing this as it seems to be resolved by various other changes.

Any update on this? I’m blocked and none of the proposed fixes has worked for me without causing additional errors.

For me the solution was downgrading to 1.3.0