Adding camera api to react native

React Native has a native Camera component billed as
"The comprehensive camera module for React Native. Including photographs, videos, and barcode scanning!"

Sounds cool, and the installation looks to be easy going by the instructions at
https://github.com/react-native-community/react-native-camera

Note: This guide assumes you have already built a basic react native app using
> create-react-native-app dev-app-01
or whatever cooler name you gave your app
and you want to add camera functionality to prototype an app

And you have set up your node js, react native, android sdk environment, and ejected your react native app; if not you can follow the guide Eject your react native app!

And the adventure begins:

> npm install react-native-camera --save

That should work

> react-native link react-native-camera

Try running it

> react-native run-android

And the first Error #1

File C:\Users\[username]\.android\repositories.cfg could not be loaded.

To confirm that the automatic install and link methods did the right things,
read over the manual instructions to install on android (repeated below)
https://github.com/react-native-community/react-native-camera#android
Note: I had to perform steps 5 and 6; Steps 1 through 4 were done by the link command

1. > npm install react-native-camera --save
2. Open up `android/app/src/main/java/[...]/MainApplication.java
    Add import com.lwansbrough.RCTCamera.RCTCameraPackage; to the imports at the top of the file
    Add new RCTCameraPackage() to the list returned by the getPackages() method. Add a comma to the previous item if there's already something there.
3. Append the following lines to android/settings.gradle:
    include ':react-native-camera'
    project(':react-native-camera').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-camera/android')
4. Insert the following lines inside the dependencies block in android/app/build.gradle:
    compile project(':react-native-camera')
5. Declare the permissions in your Android Manifest (required for video recording feature)
    <uses-permission android:name="android.permission.RECORD_AUDIO"/>
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
6. Add jitpack to android/build.gradle
    allprojects {
        repositories {
            maven { url "https://jitpack.io" }
        }
     }

Try running  again

> react-native run-android

And the same Error #1

File C:\Users\[username]\.android\repositories.cfg could not be loaded.

So create an empty file

C:\Users\[username]\.android\repositories.cfg

Note: Make sure you already have the android emulator running
Open Android Studio
Tools -> Android -> ADV Manager aka Android Virtual Device -> Start

Try running  again

> react-native run-android

And Error #2

> Could not resolve all dependencies for configuration ':app:_debugApkCopy'.

  > Could not find com.android.support:exifinterface:26.0.2.

Manually add the dependencies to add the missing libs

Browse to

c:\Dev\ReactNativeApps\dev-app-01\android\app\build.gradle

And add the dependencies

dependencies {

  compile 'com.android.support:exifinterface:26.0.2'

  compile "com.android.support:support-v4:26.0.1"

  compile fileTree(dir: "libs", include: ["*.jar"])

  compile "com.android.support:appcompat-v7:23.0.1"

  compile "com.facebook.react:react-native:+"  

  compile project(':react-native-camera')

}

To add it
Open Android Studio
Tools -> Android -> SDK Manager
Ensure the latest android versions are enabled, and save

Try running  again

> react-native run-android

And again Error #2

You can also delete the gradle cache which may be stale from the manual android instructions above
Navigate to

C:\Users\[username]\.gradle\caches

And delete all folders

Note: Gradle is a build system used by Google for android

Gradle is similar in concept to Maven, Composer, Npm, Make, etc

Try running  again

> react-native run-android

React native via gradle will re-download all the required java packages that are set in the build.gradle

And again Error #2

Well, let’s look at the build.gradle file on GitHub for the camera project

https://github.com/react-native-community/react-native-camera/blob/master/android/build.gradle

Ok, the repositories and dependencies sections are different from the main documentation.
Let’s try them

repositories {

 mavenCentral()

 maven {

  url 'https://maven.google.com'

 }

 maven { url "https://jitpack.io" }

}

dependencies {

 compile 'com.facebook.react:react-native:+'

 compile "com.google.zxing:core:3.2.1"

 compile "com.drewnoakes:metadata-extractor:2.9.1"

 compile 'com.google.android.gms:play-services-vision:+'

 compile "com.android.support:exifinterface:26.0.2"

 compile 'com.github.react-native-community:cameraview:df60b07573'

}

Try running  again

> react-native run-android

And Error #3

> Manifest merger failed : Attribute meta-data#android.support.VERSION@value value=(26.0.2) from [com.android.support:exifinterface:26.0.2] AndroidManifest.xml:25:13-35
is also present at [com.android.support:support-v4:26.0.1] AndroidManifest.xml:28:13-35 value=(26.0.1).
Suggestion: add 'tools:replace="android:value"' to <meta-data> element at AndroidManifest.xml:23:9-25:38
to override.

Going by the Q&A section of the documentation
https://github.com/react-native-community/react-native-camera#q--a

Comment out the dependency

  compile 'com.google.android.gms:play-services-vision:+'

Try running  again

> react-native run-android

And Error #4

Error: Cannot create directory C:\Dev\ReactNativeApps\DevApp02\android\app\build\intermediates\incremental\mergeDebugResources\merged.dir\values

Perhaps this exceeds window directory length
So navigate there and create it manually
C:\Dev\ReactNativeApps\DevApp02\android\app\build\intermediates\incremental\mergeDebugResources\merged.dir
Values

Try running  again

> react-native run-android

And again Error #4

So try deleting the build folder

C:\Dev\ReactNativeApps\DevApp02\android\app\build\

Hmm .. back to Error #3
Going by the Q&A section of the documentation
https://github.com/react-native-community/react-native-camera#q--a

exclude group: "com.android.support"

And force exifinterface:26.0.2

repositories {

mavenCentral()

maven { url 'https://maven.google.com' }

maven { url "https://jitpack.io" }

}

dependencies {

  compile "com.android.support:appcompat-v7:23.0.1"

  compile 'com.facebook.react:react-native:+'

  compile "com.google.zxing:core:3.2.1"

  compile "com.drewnoakes:metadata-extractor:2.9.1"

  compile ('com.android.support:exifinterface:26.0.2') {

      force = true;

  }

  compile (project(':react-native-camera')) {

      exclude group: "com.android.support"

  }

  compile fileTree(dir: "libs", include: ["*.jar"])

}

Try running  again

> react-native run-android

Well, no console errors
So try to launch the basic default app .. and that now works again

Optimistic -sign-

Add the camera example code from the main doc
https://github.com/react-native-community/react-native-camera#usage
Try running again

> react-native run-android

And Error #5

The react native red screen

Instead of trying to debug that, let’s try using the example app checked into GitHub
https://github.com/react-native-community/react-native-camera/blob/master/RNCameraExample/App.js

Try running  again

> react-native run-android

And Error #6

bundling failed: Error: Unable to resolve module `./assets/ic_photo_camera_36pt.png`

So browse the GitHub project, and there is an assets/ directory
Copy all those to your project
It is easier to git clone the project or download it as a zip and copy the assets/ folder over
https://github.com/react-native-community/react-native-camera

Try running  again

> react-native run-android

And Error #7

cannot load index.android.js

Per a git issue thread

https://github.com/facebook/react-native/issues/15388

adb reverse tcp:8081 tcp:8081

Adb was not in my path, so I had to

C:\Users\[username[\AppData\Local\Android\sdk\platform-tools\adb reverse tcp:8081 tcp:8081

Try running  again

> react-native run-android

And Error #8

A white screen

Trying another option in the git issue thread
https://github.com/facebook/react-native/issues/15388#issuecomment-356937491

Shake the phone -sign- to show developer options for react native
Choose Dev Settings
Tap Debug server host and port for device
Enter your laptops IP and port 8081

Note: You can get your IP from the command prompt

> ipconfig

Try running  again

> react-native run-android

And hey, it actually works.
Cool.

There was a lot of environment initialization and fixing from the joys of rapid development libraries and multiple complex build tools, but at least the camera api is available and -currently- works.

Now to actually designing an app.
Till next time.

End of document. Thanks for reading.

Eject your react native app!

Ejecting your react native app just means you can use native java and objective c code and components in your react native app

Background:

While this started as a 'simple' guide to install a camera component in react native, it ends up being a guide to eject your react native app and run it in the android emulator, as preparation to using the camera component.

Note: This guide assumes you have already built a basic react native app using

> create-react-native-app dev-app-01

or whatever cooler name you gave your app and you want to add camera functionality to prototype an app

Impetuous:

React Native has a native Camera component billed as 

"The comprehensive camera module for React Native. Including photographs, videos, and barcode scanning!"
Sounds cool, and the installation looks to be easy going by the instructions at

https://github.com/react-native-community/react-native-camera

And the adventure begins:

> npm install react-native-camera --save

That should work

> react-native link react-native-camera

And the first Error #1
The term 'react-native' is not recognized

You need to install react native global

> npm install -g react-native-cli

And the next Error #2
`react-native link` can not be used in Create React Native App projects.
So let's go with the manual instructions at

https://github.com/react-native-community/react-native-camera

First, to use native components, you have to 'eject' your project
Ejecting just means you can use native java and objective c code and components in your app

> npm run eject

This will create android and ios folders where you can customize the java and objective c code directly, or in the case of trying to use the camera component, add components which are written in java and objective c

Answer a few questions such as what's your project name.
I choose to not create an Expo account at this time, as uhg another account, and their site was not responding tonight.  While using the Expo app on your phone is easier than manually copying your app from your notebook to your phone, the android emulator should work for now for quick testing.> npm start

And the next Error #3
will complain that you are running a react native app so now you have to start with android

trying again

>  react-native run-android

And the next Error #4
SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

So now you have to install android studio to get the android sdk

It's best to follow the full page of instructions at

https://facebook.github.io/react-native/docs/getting-started.html

Make sure you click the appropriate buttons
'Building Projects with Native Code'
'Windows'
'Android'
And then follow their lengthy instructions.

• Download and install android studio (683MB + GBs for SDKs and emulators), 
• Make sure you have the appropriate SDKs checked - the defaults worked for me
• And add a PATH variable

trying again

>  react-native run-android

And the Error #4 again
SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

Double check that you entered the PATH in Android Studio
But that still didn't work for me,

So I created a local.properties file in the android/ folder and added

> sdk.dir = C:/Users/[username]/AppData/Local/Android/sdk

trying again

>  react-native run-android

And the next Error #5
Could not find tools.jar. Please check that C:\Program Files\Java\jre1.8.0_151 contains a valid JDK installation.

Which means you need to install the Java Development Kit aka JDK
Which makes sense as the java code will need to be compiled
Download and install the JDK

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

trying again

>  react-native run-android

And the next Error #6
com.android.builder.testing.api.DeviceException: No connected devices!
Which means the android emulator needs to be running
So
Android Studio
Tools -> Android -> ADV Manager aka Android Virtual Device

Create a new device
Choose Pixel 2 XL since that is fairly new
Next Next Next, just using the defaults

Click the Play button

Wait for it..
And the android emulator should be running

trying again

>  react-native run-android

Hmmm, no immediate errors
Click the app drawer (the up caret above the gmail icon)
Your app should be in the top right
Drag it to the home screen and click

And the next Error #7
Error: Couldn't find preset "babel-preset-react-native-stage-0/decorator-support" relative to directory

Note: Babel is a JavaScript transpiler. Babel enables us to write modern ES6/7 JavaScript that will be "transpiled" to widely-supported ES5 JavaScript.

So install the babel preset

> npm install babel-preset-react

> babel-preset-react-native-stage-0

trying again

>  react-native run-android

And the next Err .. no wait, it works!
Nice

With the android emulator window active, press Ctrl+M to bring up the react native context menu

Select Enable Hot Reloading

Make a change to some text in your app.js
And its updated in the phone app
Cool

OK, I didn't get to the actual camera part this time,
but there was a lot of environment initialization, and the basics seem to be working.

So till next time..

End of document. Thanks for reading.

git and line endings, .gitattributes

If you develop in Windows, and deploy to Linux, and use git,
you may run into issues where Linux configuration files end up with Windows new lines ie carriage return and new line ie \r\n, thus preventing your Linux configuration from working.

Note: Check if you have the default git option of config.autocrlf=true set, or are required to by your company policy.

To keep your Linux configuration files 'clean' with just new lines ie \n
you can override certain directories or files to use a specific line ending, such as \n.
Git provides additional settings by placing a file named

.gitattributes

in either your code repository root, or in a subdirectory.

Note: Windows explorer will not allow you to create a dot file ie .gitattributes or .htaccess
You can copy an already created or downloaded file, and edit it, or from the command line

> echo > .gitattributes

or

> rename newdocument.txt .gitattributes

To let Git handle the automagic line endings conversion for you, on commits and checkouts. Binary files won't be altered, files detected as being text files will see the line endings converted on the fly.

> echo .gitattributes

* text=auto

You can also add additional criteria to specify whether a file is text, thus auto convert line endings, or binary, do nothing.

> echo .gitattributes

# text; auto convert line endings

*.txt text

*.h text

# binary; do not do anything

*.jpg binary

*.data binary

You can also ensures that all files that match a pattern have normalized line endings in the repository by adding a eof property; eof can be lf or crlf

> echo .gitattributes

# Ensure shell and conf files use LF.

*.sh         eol=lf

*.conf       eol=lf

*.bash       eol=lf

A large example of .gitattributes on GitHub

End of document. Thanks for reading.

git and line endings, core.autocrlf

Ah line endings; \r\n vs \n

Some OSes, such as Windows, prefer carriage returns and new lines: (\r\n)

While others, such as Linux and Mac, prefer new lines: (\n)

This default preference is not a problem, until you start sharing code across OSes using a version control system, like git.

For example, if your Windows ide enters \r\n for new lines, or worse, on save converts all lines to \r\n, while another developer's Linux ide enters \n for new lines, and also on save converts all lines to \n, the version control system will mark all affected lines as changed, when really it was just line endings.

To minimize the unintentional changing of line endings:
1) Developers can agree on the desired line ending and adjust their ide to save as such.
The desired line ending often depends on whether the target OS for the code is Linux or Windows, matching the OS preference.
2) Git by default can help manage line endings on commits and checkouts, by setting the config flag:

core.autocrlf

config.autocrlf=true

If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point. This is because Windows uses both a carriage-return character and a linefeed character for newlines in its files, whereas Mac and Linux systems use only the linefeed character. This is a subtle but incredibly annoying fact of cross-platform work; many editors on Windows silently replace existing LF-style line endings with CRLF, or insert both line-ending characters when the user hits the enter key.
Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true – this converts LF endings into CRLF when you check out code:

> git config --global core.autocrlf true

config.autocrlf=input

If you’re on a Linux or Mac system that uses LF line endings, then you don’t want Git to automatically convert them when you check out files; however, if a file with CRLF endings accidentally gets introduced, then you may want Git to fix it. You can tell Git to convert CRLF to LF on commit but not the other way around by setting core.autocrlf to input:

> git config --global core.autocrlf input

This setup should leave you with CRLF endings in Windows checkouts, but LF endings on Mac and Linux systems and in the repository.

config.autocrlf=false

If you’re a Windows programmer doing a Windows-only project, then you can turn off this functionality, recording the carriage returns in the repository by setting the config value to false:

> git config --global core.autocrlf false

Note: Above 2) sourced from Git Book

This is the recommended option if you want to manage line endings yourself; no magic = good

Note: You can also manually edit the git global config by editing the file in

> echo C:\Users\[username]\.gitconfig

[user]

name = first last

email = your@email.com

[core]

autocrlf = true

   

Further reading on StackOverflow

End of document.  Thanks for reading.