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.

Error with linking

See original GitHub issue

I had to manually link it to <appRoot>MainApplication.java

import com.apsl.versionnumber.RNVersionNumberPackage;  <-- add this
@Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
	  new RNVersionNumberPackage(),  <-- add this
          new MainReactPackage()
      );
    }
`

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:6

Top GitHub Comments

3reactions

Azmeer-crescentcommented, Feb 9, 2018

What I meant was, the normal react-native link did link the settings.gradle and build.gradle properly, but it DID NOT process the MainApplication.java for some reason.

0reactions

EleeMosinarYcommented, Sep 23, 2019

Just did yarn install react-native-version-number then react-native link react-native-version-number and it worked flawlessly:

rnpm-install info Linking react-native-version-number ios dependency 
rnpm-install info Platform 'ios' module react-native-version-number has been successfully linked 
rnpm-install info Linking react-native-version-number android dependency 
rnpm-install info Platform 'android' module react-native-version-number has been successfully linked

Did same thing still getting undefined in build number and all 3 in ios