React-native: ld: library not found for -lGoogleAnalyticsServices

Created on 19 Dec 2019  路  5Comments  路  Source: facebook/react-native

Hi,

I am upgrading react-native version from 0.59.10 to 0.61.5 and I have some issues with building iOs project.

I was upgrading by this helper: https://react-native-community.github.io/upgrade-helper/?from=0.59.10&to=0.61.5

When I am building to iOs, all time I have error like this:
ld: library not found for -lGoogleAnalyticsServices

In my project I am using react-native-google-analytics-bridge

Xcode version: 10.2.1

Could you help me to resolve this issue, please?

Thank you 馃檹

React Native version: 0.61.5

Bug Stale

Most helpful comment

easy fix for this is to remove the google analytics bridge comething in your package.json and remove it from the podfile and then remove node_modules and pod.lock.

  1. Remove google analytics bridge from package.json
  2. Remove node_modules
  3. Remove googel analytics bridge from podfile
  4. Remove pod.lock file
  5. yarn install
  6. pod install

and it should work. Why I think it does not work is cuz it says it is deprecated and it won't download the package and that is why podfile cant find it

All 5 comments

react-native-google-analytics-bridge is deprecated and probably not updated to support auto-linking, thereby your issue with the library not being found. see repo

You should convert to firebase analytics.

easy fix for this is to remove the google analytics bridge comething in your package.json and remove it from the podfile and then remove node_modules and pod.lock.

  1. Remove google analytics bridge from package.json
  2. Remove node_modules
  3. Remove googel analytics bridge from podfile
  4. Remove pod.lock file
  5. yarn install
  6. pod install

and it should work. Why I think it does not work is cuz it says it is deprecated and it won't download the package and that is why podfile cant find it

thank you past me for helping future me <3

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.

Was this page helpful?
0 / 5 - 0 ratings