'GoogleUtilities/GULAppEnvironmentUtil.h' file not found

ios firebase cocoapods google-analytics-sdk
Prateek Roy picture Prateek Roy · Aug 20, 2018 · Viewed 21.4k times · Source

Trying to compile my project after adding some pods. While compiling it gives below error

'GoogleUtilities/GULAppEnvironmentUtil.h' file not found

Podfile.lock snippet 

- FirebaseCore (5.1.1):
        - GoogleUtilities/Logger (~> 5.2)
      - FirebaseDynamicLinks (3.0.2):
        - FirebaseAnalytics (~> 5.1)
      - FirebaseInAppMessaging (0.11.0):
        - FirebaseAnalytics (~> 5.1)
        - FirebaseCore (~> 5.1)
        - FirebaseInstanceID (~> 3.2)
        - GoogleUtilities/Environment (~> 5.0)
      - FirebaseInstanceID (3.2.1):
        - FirebaseCore (~> 5.1)
        - GoogleUtilities/Environment (~> 5.2)
      - FirebaseMessaging (3.1.0):
        - FirebaseCore (~> 5.0)
        - FirebaseInstanceID (~> 3.0)
        - GoogleUtilities/Reachability (~> 5.2)
        - Protobuf (~> 3.1)
      - FirebaseRemoteConfig (3.0.1):
        - FirebaseABTesting (~> 2.0)
        - FirebaseAnalytics (~> 5.1)
        - FirebaseCore (~> 5.1)
        - FirebaseInstanceID (~> 3.2)
        - GoogleUtilities/Environment (~> 5.2)
        - "GoogleUtilities/NSData+zlib (~> 5.2)"
        - Protobuf (~> 3.5)
      - Google/Analytics (2.0.4):
        - Google/Core
        - GoogleAnalytics (~> 3.12)
      - Google/Core (2.0.4):
        - GoogleInterchangeUtilities (~> 1.0)
        - GoogleNetworkingUtilities (~> 1.0)
        - GoogleSymbolUtilities (~> 1.0)
        - GoogleUtilities (~> 1.1)

Answer

Paul Beusterien picture Paul Beusterien · Aug 20, 2018

In the Podfile, change Google/Analytics to GoogleAnalytics. The Google pod is deprecated and not compatible with recent Firebase versions.

An alternative, but not recommended workaround, could be to lock the Firebase version to something less than 5.5.

UPDATE: June 2021: There is a Crashlytics podspec bug that can also cause this issue. The workaround is to explicitly add GoogleUtilities/Environment to the Podfile or move use_frameworks! to the top of the Podfile. Details in https://github.com/firebase/firebase-ios-sdk/issues/8137. The issue will be fixed in the upcoming Firebase 8.3.0 release.

Related questions

Framework not found GoogleToolboxForMac

After I update my Firebase via "pod update", I got error like this : ld: warning: directory not found for option '-F/Users/bennysantoso/Library/Developer/Xcode/DerivedData/FCM-atfcxuircoryufazlomgwfgmvaqm/Build/Products/Debug-iphonesimulator/GoogleToolboxForMac' ld: framework not found GoogleToolboxForMac clang: error: linker …

Read More
CocoaPods could not find compatible versions for pod "Firebase/Core” | cloud_firestore, Flutter

I am having some issues in the pod, see below Launching lib/main.dart on iPhone X in debug mode... Running pod install... CocoaPods' output: ↳ Preparing Analyzing dependencies Inspecting targets to integrate Using `ARCHS` setting to build architectures of target `…

Read More
Flutter: CocoaPods's specs repository is too out-of-date to satisfy dependencies

Current, I was trying to add firebase_core: ^0.5.0+1 and firebase_crashlytics: ^0.2.1+1 packages in my flutter project with the latest versions, It works without any trouble in Android but in iOS, it is not working and giving error. So now how …

Read More