This needs a more thorough investigation.

1. Followed the readme, added this on a "already built app" (ie run-android ran at least once before)
2. Had issue with cannot require index.js`
3. Removed app (uninstall), run-android, put live reload back and node app was terminated right when launched
4. Removed again (uninstall), now it's fine can run http server and request

I think that there's something going on when I launch run-android a second time, the node app isn't updated?
I'll let you know if I can reproduce this or improve DX somehow.

error info:

CANNOT LINK EXECUTABLE: cannot locate symbol "sigfillset" referenced by "/data/data/com.XXXXX.XXXX

Are you aware of this repo?

https://github.com/janeasystems/nodejs-mobile

Do you plan on adding iOS support soon?

Hello again,
I am trying to run a timer on the server that executes a certain function every x seconds.
Something like:

setTimeout(function() {
  // work
}, delay);

and notifies the main thread each time. However, seeing as the server in your example relies on Express, each request receives an answer once, and I have to fetch the URL again to execute it, and I'm kinda reluctant here as every bit of performance is crucial in this particular project.

What I'm aiming at really is something along the lines of a Worker, something like:

worker.onmessage = message => {
  switch(message) {
    case 'periodicAction':
    // Execute a function, return the result
    worker.postMessage('My result')
    default
    worker.postMessage('Do nothing...')
  }
};

What I'm getting at really is: Is there a way to get rid of Express and replace the node thread with a fullblown worker?
And if not, is there some way to have it perform some kind of task periodically and notify the main thread when it's done each time? Something like:

RNNode.sendMessage('a message')

I apologize for creating an issue, as this is not really one
Again, thank you

This project links to a couple other projects at the top of the readme, but there's no mention of nodejs-mobile which at first glance appears to do the same thing but also for ios?

While using this library for a simple fs.readFile method in ./background, I am getting this error while building the project. I followed all the instruction.

C:\path\to\project\node_modules\react-native-node\android\src\main\java\com\staltz\reactnativenode\RNNodePackage.java:23: error: method does not overr
ide or implement a method from a supertype
    @Override                                                  
    ^
1 error
:react-native-node:compileReleaseJavaWithJavac FAILED

Project specs

"react": "^16.0.0-alpha.12",
"react-native": "^0.47.1",
"react-native-node": "^1.1.2"

Any clue ?

Hello,
Is there some way to add es7 support to the background folder? Porting code from other projects that rely of async/await is proving challenging

First of all: Thanks for this project!

I am checking out the /example code and when running as described in the README and without modifications I get following error:

TypeError: Network request failed
    at XMLHttpRequest.xhr.onerror (fetch.js:441)
    at XMLHttpRequest.dispatchEvent (event-target.js:172)
    at XMLHttpRequest.setReadyState (XMLHttpRequest.js:546)
    at XMLHttpRequest.__didCompleteResponse (XMLHttpRequest.js:381)
    at XMLHttpRequest.js:485
    at RCTDeviceEventEmitter.emit (EventEmitter.js:181)
    at MessageQueue.__callFunction (MessageQueue.js:260)
    at MessageQueue.js:101
    at MessageQueue.__guard (MessageQueue.js:228)
    at MessageQueue.callFunctionReturnFlushedQueue (MessageQueue.js:100)

I will look into this further, but maybe there is something obvious I am overlooking..

(Versions: yarn 0.24.6, npm 4.2.0, ubuntu 16.04, (local) node: 7.10.1)

PS I will try again with downgraded node on ubuntu system

Hi there,

I've followed the readme and have applied what has been told, but build fails everytime.

android\build.gradle

// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    repositories {
        jcenter()
        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.0.0'
        classpath 'com.google.gms:google-services:3.1.2'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        mavenLocal()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
        maven {
            url 'https://maven.google.com'
        }
    }
}

app\build.gradle

...
def enableProguardInReleaseBuilds = false
android {
    compileSdkVersion 25
    buildToolsVersion '26.0.2'

    defaultConfig {
        applicationId "com.heartfailure"
        minSdkVersion 16
        multiDexEnabled true
        targetSdkVersion 22
        versionCode 1
        versionName "1.0"
        ndk {
            abiFilters "armeabi-v7a", "x86"
        }
    }
...
    buildTypes {
        release {
            minifyEnabled enableProguardInReleaseBuilds
            proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
        }
    }
...
}

dependencies {
    compile(project(':react-native-firebase')) {
        transitive = false
    }
    compile project(':react-native-config')
    compile fileTree(dir: "libs", include: ["*.jar"])
    compile "com.android.support:appcompat-v7:25.2.0"
    compile "com.facebook.react:react-native:+"  // From node_modules
    compile "com.google.android.gms:play-services-base:11.6.0"
    compile "com.google.firebase:firebase-core:11.6.0"
    compile "com.google.firebase:firebase-database:11.6.0"
}

// Run this once to be able to run the application with BUCK
// puts all compile dependencies into folder libs for BUCK to use
task copyDownloadableDepsToLibs(type: Copy) {
    from configurations.compile
    into 'libs'
}

apply plugin: 'com.google.gms.google-services'

MainApplication.java

package com.heartfailure;
import com.staltz.reactnativenode.RNNodePackage;
...

public class MainApplication extends Application implements ReactApplication {

  private final ReactNativeHost mReactNativeHost = new ReactNativeHost(this) {

    @Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
        new MainReactPackage(),
            new RNNodePackage(),
        new ReactNativeConfigPackage(),
        new RNFirebasePackage(),
        new RNFirebaseDatabasePackage()
      );
    }

Error

\MyApp\android\app\src\main\java\com\heartfailure\MainApplication.java:6: error: package com.staltz.reactnativenode does not exist
import com.staltz.reactnativenode.RNNodePackage;
                                 ^
C:\King's_College_London\Final_Year_Project\HeartFailure\android\app\src\main\java\com\heartfailure\MainApplication.java:29: error: cannot find symbol
            new RNNodePackage(),
                ^
  symbol: class RNNodePackage
2 errors


FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

* Get more help at https://help.gradle.org

BUILD FAILED in 23s
68 actionable tasks: 65 executed, 3 up-to-date

I'm running a simple express server like the example, and it works. But after changing the nodejs server and rebuilding with cd server && npm i && cd .. && react-native-node insert ./server the changes don't take effect any more.

I've tried deleting node_modules on both the nodejs and the react-native apps, tried deleting the rnbundle that gets saved to the raw folder. Nothing changes the express app once it's been built for the first time.

The README at the FAQ section has some text I do not fully understand:

Does it support packages with native bindings?

Yes, in theory, but that's the job of individual libraries having native bindings for android. Most packages don't have. I believe sodium-native has. Hint: if you want to compile the native part of packages, I recommend not trying to cross-compile. Instead, install termux on an Android device and compile from the phone directly.

I assume you mean node packages having native libraries, that require extra care to include. And not the native Java in react-native Gradle projects?

So not these kind of projects in the settings.gradle:

include ':react-native-maps'
project(':react-native-maps').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-maps/android')
include ':react-native-randombytes'
project(':react-native-randombytes').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-randombytes/android')
include ':react-native-i18n'
project(':react-native-i18n').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-i18n/android')

It would be nice if there was an example that e.g. included the native parts of sodium-native as a demonstration of how to bundle / use that in a project (besides compiling it). Apart from that an explanation or pointer to more compilation instruction would be great.

PS I am looking into node-as-native-libray projects to avoid having to use termux. You can't offer that to end-users. But it is just needed for compilation purposes, not for installing app, right?

Thanks!

Hello,
is there some way to run react-native-node insert ./background on app reload? Because as things stand I have to test my code in a separate project before using it in the background folder.

It's not an issue per se, but a substantial improvement that could be made.

Thank you.

^{And please continue working on IOS support, I tested nodejs-mobile and it's just bad... (awfully slow)}

Hi I'm really amazed by the project.

Anyways:

• Can it run child processes?
• Can it execute another process as node too?

I know this isn't stackoverflow but I'm really clueless about the posaibility, or if so, how.

Thank you.

This is a follow-up to #2

For my stackoverflow question on 4 possible solutions, I receive an answer from the NodeBase creator, basically stating that his project is a 'plaything' and J2V8 the best approach.

To me J2V8 (created by @irbull) looks like the most stable implementation currently, leading to my question: Why did you opt for NodeBase?

It seems to me with J2V8 you'd gain:

• a much more active project
• support for newer Node versions (currently 7.6.0, but 8.x just PR'ed)
• additional features:
  • 2-way js-to-java bridge (call java from script and vice versa)
  • 2-way integrated error / exception handling
  • chrome debugging support
  • full build environment with docker-based cross-compile for unix, mac, windows and android
  • more smaller stuff ...

Hi,

This is just a FYI, feel free to close.

I just found your project after I created a SO question on pro's / con's of different approaches: : Compiling NodeJS as native library on Android

I am not familiar to the native linking, compiling techniques in bringing Node to android, so find it hard to choose between options, but your project looks like it is exactly what I am looking for! Thank you.

PS I updated the SO question with react-native-node link.

Is it a way to expose this server to the public? Maybe with something like https://www.npmjs.com/package/no-ip