Use of package name in rnpm-prelink.sh

I encountered the following issue when linking the module for Android in my current project:

react-native link react-native-spinkit
RNSpinkit checking app version ..
RNSpinkit patching MainApplication.java ..

<PROJECT_PATH>/node_modules/react-native-spinkit/scripts/rnpm-prelink.js:71
    throw 'RNSpinkit could not link Android automatically, MainApplication.java not found in path : ' + APPLICATION_MAIN
    ^
RNSpinkit could not link Android automatically, MainApplication.java not found in path : <PROJECT_PATH>/android/app/src/main/java/com/<PACKAGE_NAME>/MainApplication.java
<PROJECT_PATH>/node_modules/react-native/local-cli/core/makeCommand.js:19
        throw new Error(`Error occured during executing "${ command }" command`);
        ^

Error: Error occured during executing "node ./node_modules/react-native-spinkit/scripts/rnpm-prelink.js" command
    at ChildProcess.prelink (<PROJECT_PATH>/node_modules/react-native/local-cli/core/makeCommand.js:19:15)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:852:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

It turns out that the problem was that the script assumes that your project name is the same as the package name, which wasn't the case in my project (the package name had a suffix, -mobile) in the package name to avoid package naming collisions.

Start with scripts/rnpm-prelink.js around line 71 and trace how the Android MainApplication.java path is assembled during react-native link. Reproduce the case where the project name and package name differ, then verify that linking locates the actual application package and completes without this error.