What to do when try to release application

Firstly, thank you for this great project. Comparing to the original approach, this one is much handier 👍

Everything works perfectly when developing, however, stuck when trying to generate a release version.

Errors like the followings:

```
ReactNativeJS: Module AppRegistry is not a registered callable module (calling runApplication)
ReactNativeJS: Unable to symbolicate stack trace: Bundle was not loaded from the packager
```

Although this project is mainly used to facilitate the usage of `figwheel` when development, eliminating this library (for example, don't use bridge to _startApp_) and execute something like `clj -A:fig -m figwheel.main -O advanced -bo prod` seems still working.

However, when generating a released APK, it would crash as soon as launching the application. The major reason is ```cljsExports``` is undefined. The tricky thing comes here, when `react-native run-*`, this `cljsExports` could be loaded while what should we do when issuing the release one?

There is another option to drawback to using `lein` related configuration, however, it would lose the convenience of direct *ns* name mapping.

Any recommendation?

The issue names no files or tests; start by reproducing the release APK crash and compare cljsExports availability between react-native run-* and the release build. Done means the generated APK launches without the AppRegistry or cljsExports-related errors described here.

Written by the indexing model from the issue text.