question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

React Native CLI uses autolinking for native dependencies, but the following modules are linked manually

See original GitHub issue

Hi!

Environment

System:
    OS: macOS 10.14.6
    CPU: (6) x64 Intel(R) Core(TM) i5-8500B CPU @ 3.00GHz
    Memory: 11.94 GB / 32.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.16.1 - /var/folders/gc/xkqxhrb553zcx8qktfhjbs500000gn/T/yarn--1568942511525-0.4078540298679072/node
    Yarn: 1.17.3 - /var/folders/gc/xkqxhrb553zcx8qktfhjbs500000gn/T/yarn--1568942511525-0.4078540298679072/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.1/bin/npm
  SDKs:
    iOS SDK:
      Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    Android SDK:
      API Levels: 23, 25, 27, 28, 29
      Build Tools: 25.0.2, 25.0.3, 28.0.3, 29.0.1, 29.0.2
      System Images: android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
  IDEs:
    Android Studio: 3.5 AI-191.8026.42.35.5791312
    Xcode: 11.0/11A419c - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.5 => 0.60.5
└─ react-native-vector-icons@6.6.0

Description

  1. yarn add react-native-vector-icons
  2. Added pod 'RNVectorIcons', :path => '../node_modules/react-native-vector-icons' to Podfileandpod update` has been runned
  3. All is working now, but I see warning after react-native run-ios:

React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:

  • react-native-vector-icons (to unlink run: “react-native unlink react-native-vector-icons”) This is likely happening when upgrading React Native from below 0.60 to 0.60 or above. Going forward, you can unlink this dependency via “react-native unlink <dependency>” and it will be included in your app automatically. If a library isn’t compatible with autolinking, disregard this message and notify the library maintainers. Read more about autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md

Want to say again, it’s not break app work.

Is it expected warning or I did something wrong?

Thanks.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:7

github_iconTop GitHub Comments

35reactions
websitedesignanddevelopercommented, Sep 20, 2019

You don’t need add entry of library inside the pod file. Just follow these steps.

  1. yarn add react-native-vector-icons
  2. cd pod and pod install
  3. Then inside info.plist add property Fonts provided by application Like described here https://github.com/oblador/react-native-vector-icons#option-manually
  4. then react-native run-ios That’s it. Warning will go away.
0reactions
abduljeleelngcommented, May 20, 2020

@websitedesignanddeveloper and all, yarn add react-native-vector-icons However, if I did not link “react-native link react-native-vector-icons” Icons will not display, however, App is working fine. but if I link with “react-native link react-native-vector-icons” Icons will display and App work fine but I received this warning error. error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually:

* react-native-vector-icons (to unlink run: "react-native unlink react-native-vector-icons")
  This is likely happening when upgrading React Native from below 0.60 to 0.60 or above. Going forward, you can unlink this dependency via "react-native unlink " and it will be included in your app automatically. If a library isn't compatible with autolinking, disregard this message and notify the library maintainers.
  Read more about autolinking: https://github.com/react-native-community/cli/blob/master/docs/autolinking.md
  info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
  Jetifier found 1015 file(s) to forward-jetify. Using 4 workers...
  info Starting JS server...

I followed the second method from the documentation, and It really helpful The instructions as follow : (It from official documentation

Android Option: With Gradle (recommended)

This method has the advantage of fonts being copied from this module at build time so that the fonts and JS are always in sync, making upgrades painless.

Edit android/app/build.gradle ( NOT android/build.gradle ) and add the following:

apply from: “…/…/node_modules/react-native-vector-icons/fonts.gradle”

Read more comments on GitHub >

github_iconTop Results From Across the Web

error React Native CLI uses autolinking for ... - Stack Overflow
I got this error "React Native CLI uses auto linking for native dependencies, but the following modules are linked manually ...
Read more >
Linking Libraries - React Native
Here are the few steps to link your libraries that contain native code​. Automatic linking​. Install a library with native dependencies: npm ...
Read more >
React Native CLI uses autolinking for native dependencies ...
[Solved]-React Native CLI uses autolinking for native dependencies, but the following modules are linked manually react-native-webview-React Native.
Read more >
Autolinking Native Modules · React Native for Windows + ...
Autolinking is a mechanism that allows your React Native app project to discover and use native modules and view managers provided by React...
Read more >
Running the React Native App in Linux - Joplin Forum
... error React Native CLI uses autolinking for native dependencies, but the following modules are linked manually: - react-native-camera (to unlink run: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found