Giter VIP home page Giter VIP logo

ueno-llc / react-native-starter Goto Github PK

View Code? Open in Web Editor NEW
573.0 26.0 91.0 16.33 MB

Professional react-native starter kit with everything you'll ever need to deploy rock solid apps

Home Page: https://ueno-llc.github.io/react-native-starter

License: MIT License

Java 15.22% JavaScript 3.99% Ruby 25.21% Objective-C 11.45% Shell 24.58% TypeScript 15.88% Starlark 3.68%
react-native react-native-starter typescript mobx-state-tree cocoapods firebase push-notifications appcenter

react-native-starter's Introduction

WARNING

This starter kit has been deprecated and is no longer being actively maintained by Ueno.

logo

banner

about

React Native Starter

Dependencies devDependencies

The Professional React Native Starter with everything you'll ever need to deploy rock solid apps.

  • Opinionated dependencies
  • React Native Navigation 4
  • TypeScript 3.7
  • Auto Linking
  • Gradle 5
  • Unit and integration tests
  • Continuous delivery support for Microsoft App Center

Getting Started

Super-Quick Start

git clone [email protected]:ueno-llc/react-native-starter.git my-new-app
cd my-new-app
yarn
yarn rename "MyNewApp" com.ueno.mynewapp
yarn start
yarn ios # or yarn android

Alternatively you can use create-ueno-app:

yarn create ueno-app native my-new-app co.ueno.mynewapp

Running automated tests

iOS

yarn build:e2e:ios
yarn test:e2e:ios

Note: To see the testing in-action, open the iPhone X Simulator manually before running the tests.

Android

yarn build:e2e:android
yarn test:e2e:android

Note: You will need to create Emulator with the name Pixel_2_API_28 in Android Studio.

Documentation

The documentation is available here on GitHub Pages.

We also recommend the following reading material:

Upgrading

No plans have been made so far to upgrade. We only support merging from upstream for now.

Contributing

If you are interested in helping out, feel free to submit issues, pull-requests or even contact us. We are open to all kind of contributions.

License

This project is MIT licensed

react-native-starter's People

Contributors

amurmurmur avatar birkir avatar bjarnif avatar daviswhitehead avatar dependabot[bot] avatar designorant avatar dgobaud avatar elliottkember avatar greenkeeper[bot] avatar greenkeeperio-bot avatar isaachinman avatar jeremybarbet avatar natedonato avatar zachheine avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

react-native-starter's Issues

CocoaPods could not find compatible versions for pod "Sentry"

Im using mac os, when I run the command yarn install im getting this output:
Any idea?

[!] CocoaPods could not find compatible versions for pod "Sentry":
  In Podfile:
    SentryReactNative (from `../node_modules/react-native-sentry`) was resolved to 0.40.2, which depends on
      Sentry (~> 4.0.1)

None of your spec sources contain a spec satisfying the dependency: `Sentry (~> 4.0.1)`.

You have either:
 * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
 * mistyped the name or version.
 * not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

Documentation

My observations for the past weeks have been the following:

  • How do environment variables and .env_example work in CI. All variables that should be exposed to the app should be set in .env_example.
  • SCSS/Stylus/LESS imports DO NOT WORK. Don't attempt to use them.
  • How do those certificates work and what do I need to do to get going with app center.

Can't link external libraries

Scanning folders for symlinks in /Users/elliott/ueno/UenoDesign2/node_modules (14ms)
rnpm-install info Linking react-native-browser ios dependency
rnpm-install ERR! Something went wrong while linking. Error: Invalid target: E3AAD4501F573E3700B7831D
Please file an issue here: https://github.com/facebook/react-native/issues

Invalid target: E3AAD4501F573E3700B7831D

Manually linking doesn't work either - no native component found for FastImageView.

The application does not start on the emulator

I run
react-native start

Then
react-native run-android

I see an error in the emulator (Android studio SDK 28 android 9)
'Error: Unable to resolve module ./index from ``:

None of these files exist:

  • index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
  • index/index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
    at ModuleResolver.resolveDependency (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:163:15)
    at ResolutionRequest.resolveDependency (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/node-haste/DependencyGraph.js:282:16)
    at /home/lomaz/www/befree_new_mobile/node_modules/metro/src/lib/transformHelpers.js:267:42
    at Server. (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/Server.js:1088:41)
    at Generator.next ()
    at asyncGeneratorStep (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/Server.js:99:24)
    at _next (/home/lomaz/www/befree_new_mobile/node_modules/metro/src/Server.js:119:9)
    ::ffff:127.0.0.1 - - [12/Sep/2019:11:31:23 +0000] "GET /index.bundle?platform=android&dev=true&minify=false HTTP/1.1" 500 - "-" "okhttp/3.12.1"
    '

I tried and it did not help
react-native start --reset-cache

GeneratedInfoPlistDotEnv.h not found

Describe the bug
Xcode build fail

To Reproduce
yarn create ueno-app native sample co.nguyen
run Xcode
build fail

Expected behavior
Build success

Screenshots
Screen Shot 2020-02-20 at 11 09 46

Environment

  • React Native Starter version: latest
  • React Native version: 0.62.0-rc1
  • Platforms
    • iOS
  • Device Info
    • Simulator in Debug

Additional context

Run react-native info in your terminal and paste its contents here.
`
System:
OS: macOS 10.15.2
CPU: (4) x64 Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz
Memory: 28.63 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 10.18.1 - ~/.nvm/versions/node/v10.18.1/bin/node
Yarn: 1.22.0 - /usr/local/bin/yarn
npm: 6.13.4 - ~/.nvm/versions/node/v10.18.1/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 14, 23, 25, 26, 28, 29
Build Tools: 23.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.3, 29.0.2
System Images: android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.6010548
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2

I found this error from react-native-config, but when I follow [this]: (lugg/react-native-config#125) and [this]: (lugg/react-native-config#365), all recommend doesn't woking, and I remove react-native-config, clean build folder, run and has the same error. I don't understand what's going on, previous version doesn't has this error.
`

Why include fastlane certs in the main repo?

I notice you have included Matchfiles in both the android and ios fastlane dirs.

I am new to RN and am just getting set up with fastlane. Can you explain your reasoning here, when the fastlane docs specifically recommend running match in a different "certificates" repo?

It seems like Bitrise already expects fastlane certs to be in a separate repo. Maybe you set it up this way to facilitate ease of use with Travis?

Will there be any serious problems with your CI/deployment setup if I pull my certs into a separate repo entirely?

Detox Issues with Xcode 10.2

Describe the bug
Xcode 10.2 doesn't support the Swift Language Version that comes with the current Detox 10.0.12

corresponding Detox issue: wix/Detox#1229

To Reproduce

With XCode 10.2 installed:

git clone [email protected]:ueno-llc/react-native-starter.git my-new-app
cd my-new-app
yarn

Expected behavior
Post install script for Detox should run successfully.

Environment

  • React Native Starter version: [2.1.0]
  • React Native version: [0.59.0-rc.3]
  • Platforms
    • iOS
    • Android
  • Device Info
    • Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

Device and Verbose Detox Logs

=== BUILD TARGET Detox OF PROJECT Detox WITH CONFIGURATION Release ===

Check dependencies
The “Swift Language Version” (SWIFT_VERSION) build setting must be set to a supported value for targets which use Swift. Supported values are: 4.0, 4.2, 5.0. This setting can be set in the build settings editor.

** BUILD FAILED **


The following build commands failed:
	Check dependencies
(1 failure)

Error on build apk file

Run ./gradlew assembleRelease and i get error

Task :app:preReleaseBuild FAILED

FAILURE: Build failed with an exception.

  • What went wrong:
    Execution failed for task ':app:preReleaseBuild'.

Could not resolve all files for configuration ':app:releaseCompileClasspath'.
Could not find com.android.support:support-v4:28.0.3.
Required by:
project :app > com.android.support:design:27.1.1
Could not find com.android.support:support-v4:28.0.3.
Required by:
project :app > project :react-native-firebase
Could not find com.android.support:support-v4:28.0.3.
Required by:
project :app > com.google.android.gms:play-services-basement:16.2.0

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.6.2/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 19s
46 actionable tasks: 2 executed, 44 up-to-date

Unable to load script from assets 'index.android.bundle'

Im running the command react-native run-android deploying in a Xioami A1 with android 9 in mac os.
The full error log is,,

    java.lang.RuntimeException: Unable to load script from assets 'index.android.bundle'. Make sure your bundle is packaged correctly or you're running a packager server.
        at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
        at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:216)
        at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:32)
        at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:243)
        at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1116)
        at com.facebook.react.ReactInstanceManager.access$900(ReactInstanceManager.java:117)
        at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:916)
        at java.lang.Thread.run(Thread.java:764)

Im trying to fix it reading from stackoverflow, because it seems a common problem

Android project doesn't execute build-env.sh leading to stale environment variable values

The XCode project executes build-env.sh to make sure config.env.js is updated but the Android project doesn't seem to. Simple fix is to create a yarn android command eg "android": "yarn build:env && react-native run-android" but would be better to make the Android gradle projects execute build-env.sh

XCode link https://github.com/ueno-llc/react-native-starter/blob/master/ios/react-native-starter.xcodeproj/project.pbxproj#L100

issue: detox

  • Not working on iOS "CFBundleIdentifier missing"
  • Timeout on Android

Can't run on Windows 10 at Android Emulator

Describe the bug
Can't make it run using Super-Quick Start on Windows 10.

To Reproduce
Steps to reproduce the behavior:

git clone [email protected]:ueno-llc/react-native-starter.git my-new-app
cd my-new-app
yarn
yarn rename "MyNewApp" com.ueno.mynewapp
react-native run-android

Expected behavior
Be able to run on emulator.

Error

Welcome to Gradle 5.4.1!

Here are the highlights of this release:
 - Run builds with JDK12
 - New API for Incremental Tasks
 - Updates to native projects, including Swift 5 support

For more details see https://docs.gradle.org/5.4.1/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

> Configure project :
MyNewApp D:\projects\test\ueno-test\android D:\projects\test\ueno-test\android
@react-native-community_async-storage D:\projects\test\ueno-test\node_modules\@react-native-community\async-storage\android D:\projects\test\ueno-test\android
app D:\projects\test\ueno-test\android\app D:\projects\test\ueno-test\android
detox D:\projects\test\ueno-test\node_modules\detox\android\detox D:\projects\test\ueno-test\android
react-native-code-push D:\projects\test\ueno-test\node_modules\react-native-code-push\android\app D:\projects\test\ueno-test\android
react-native-config D:\projects\test\ueno-test\node_modules\react-native-config\android D:\projects\test\ueno-test\android
react-native-firebase D:\projects\test\ueno-test\node_modules\react-native-firebase\android D:\projects\test\ueno-test\android
react-native-navigation D:\projects\test\ueno-test\node_modules\react-native-navigation\lib\android\app D:\projects\test\ueno-test\android
react-native-sentry D:\projects\test\ueno-test\node_modules\react-native-sentry\android D:\projects\test\ueno-test\android
react-native-version-number D:\projects\test\ueno-test\node_modules\react-native-version-number\android D:\projects\test\ueno-test\android

> Configure project :@react-native-community_async-storage
WARNING: The option setting 'android.enableD8.desugaring=false' is experimental and unsupported.
The current default is 'true'.


> Configure project :app
WARNING: The option setting 'android.enableD8.desugaring=false' is experimental and unsupported.
The current default is 'true'.


Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.4.1/userguide/command_line_interface.html#sec:command_line_warnings

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
A problem occurred evaluating project ':app'.
> A problem occurred starting process 'command './scripts/build-env.sh''

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

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':app'.
> compileSdkVersion is not specified.

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

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

BUILD FAILED in 4m 3s

error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build completed with 2 failures.

1: Task failed with an exception.
-----------
* What went wrong:
A problem occurred evaluating project ':app'.
> A problem occurred starting process 'command './scripts/build-env.sh''

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

2: Task failed with an exception.
-----------
* What went wrong:
A problem occurred configuring project ':app'.
> compileSdkVersion is not specified.

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

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

BUILD FAILED in 4m 3s

    at checkExecSyncError (child_process.js:629:11)
    at execFileSync (child_process.js:647:13)
    at runOnAllDevices (D:\projects\test\ueno-test\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:74:39)
    at buildAndRun (D:\projects\test\ueno-test\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:158:41)
    at then.result (D:\projects\test\ueno-test\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:125:12)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Environment

  • React Native Starter version: v3.0.0
  • React Native version: 0.61.0-rc.0 (2.0.1 cli)
  • Platforms
    • iOS
    • Android
  • Device Info
    • Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

Additional context


warn The following packages use deprecated "rnpm" config that will stop working from next release:
  - react-native-code-push: https://microsoft.github.io/code-push
  - react-native-sentry: https://github.com/getsentry/react-native-sentry
Please notify their maintainers about it. You can find more details at https://github.com/react-native-community/cli/blob/master/docs/configuration.md#migration-guide.
info Fetching system and libraries information...
System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
    Memory: 9.89 GB / 31.90 GB
  Binaries:
    Node: 10.16.3 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    Android Studio: Version  3.5.0.0 AI-191.8026.42.35.5791312

android build-env.sh call has wrong working directory

the new call to build-env.sh in build.gradle https://github.com/ueno-llc/react-native-starter/pull/210/files#diff-dc46f9f5dfe204e394fb41395ccd03cfR4 seems to work but it has wrong working directory i think

../../scripts/build-env.sh: line 66: ./ios/passfolio/GoogleService-Info.plist: No such file or directory
[SCRIPT build-env.sh] Warning: No GoogleService-Info.plist file in ios app directory... Added placeholder for now!
../../scripts/build-env.sh: line 71: ./android/app/google-services.json: No such file or directory
[SCRIPT build-env.sh] Warning: No google-services.json file in android app directory... Added placeholder for now!
[SCRIPT build-env.sh] Warning: No .env file found... Copied .env.public to .env!
cp: .env.public: No such file or directory
[SCRIPT build-env.sh] Building environment config
[SCRIPT build-env.sh] Using .env
cat: .env: No such file or directory
[SCRIPT build-env.sh] Generating ./src/config.env.js
[SCRIPT build-env.sh] Config built successfully

Hot Reloading not working

Hey guys, thanks so much for a such an awesome starter. Easily the best one I've seen.

Describe the bug
Hot reloading appears to not be functional on the latest version of the project. When changes are made, the "Hot Loading" message appears, but the changes are not visible.

To Reproduce
Steps to reproduce the behavior:

  1. Clone Repo
  2. Follow setup instructions in the docs
  3. Run project on an ios simulator
  4. Turn on hot reloading
  5. Make a change to the Home screen

Expected behavior
Making changes to the Home screen with Hot Reloading enabled should be visible without a manual reload.

Environment

  • React Native Starter version: v2.2.0
  • React Native version: 0.59.0-rc.3
  • Platforms
    • iOS
    • Android
  • Device Info
    • Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

Additional context

info
React Native Environment Info:
System:
OS: macOS 10.14
CPU: x64 Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz
Memory: 1.53 GB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 8.10.0 - ~/.nvm/versions/node/v8.10.0/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 5.6.0 - ~/.nvm/versions/node/v8.10.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
Build Tools: 23.0.1, 23.0.3, 24.0.0, 24.0.2, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.2, 27.0.3, 28.0.3
API Levels: 23, 24, 25, 26, 27, 28
IDEs:
Android Studio: 3.2 AI-181.5540.7.32.5056338
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
@types/react: 16.8.7 => 16.8.7
@types/react-native: 0.57.38 => 0.57.38
react: 16.8.4 => 16.8.4
react-native: 0.59.0-rc.3 => 0.59.0-rc.3

react-native run-ios not working

[Ueno RNS] Building environment config
[Ueno RNS] Using .env
Reading env from .env
Wrote to /Users/dmitrigrossman/projects/my-new-app/ios/build/Build/Products/GeneratedInfoPlistDotEnv.h
/Users/dmitrigrossman/projects/my-new-app
Copied GeneratedInfoPlistDotEnv.h and GeneratedDotEnv.m to ./node_modules/react-native-config/ios
[Ueno RNS] Generating ./src/config.env.js
[Ueno RNS] Config built successfully


** BUILD FAILED **


The following build commands failed:
	PhaseScriptExecution [CP]\ Check\ Pods\ Manifest.lock build/Build/Intermediates.noindex/MyNewApp.build/Debug-iphonesimulator/MyNewApp.build/Script-DE29A3C61EA94606C7B30F25.sh

(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/MyNewApp.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/MyNewApp.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

After installing all according to the docs I'm getting the following error when trying to run react-native run-ios.

Dependencies:

react-native-cli: 2.0.1
react-native: 0.56.0

Android Code Push configuration bug?

Line 85 in build.gradle makes the apply of codepush.gradle dependent on CODEPUSH_ACCESS_KEY - seems like a bug. Don't see anything like this in the iOS builds and CODEPUSH_ACCESS_KEY is only used in the App Center deploy scripts. I think the conditional should be removed.

https://github.com/ueno-llc/react-native-starter/blob/master/android/app/build.gradle#L85

if (project.env.get('CODEPUSH_ACCESS_KEY') != '') {
  apply from: "../../node_modules/react-native-code-push/android/codepush.gradle"
}

Unable to run the app in android

Describe the bug
A clear and concise description of what the bug is.
The project is not running in windows with android

To Reproduce
Steps to reproduce the behavior:

  1. Clone the app
  2. Run the app
    You will get the error

Expected behavior
Should run the app properly

Environment

  • React Native Starter version: 1.0.5
  • React Native version: 0.57.2
  • Platforms
    • iOS
    • [x ] Android
  • Device Info
    • [x ] Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

Additional context

Here is the exception that I am getting in android studio

Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


Failed to resolve: play-services-base
Open File


Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


Failed to resolve: play-services-base
Open File


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: runtime
Open File


Failed to resolve: common
Open File


Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.
It will be removed at the end of 2018. For more information see: http://d.android.com/r/tools/update-dependency-configurations.html


Failed to resolve: support-fragment
Open File


Failed to resolve: support-core-ui
Open File


Failed to resolve: common
Open File


FAILURE: Build failed with an exception.

* What went wrong:
Could not resolve all files for configuration ':react-native-code-push:debugCompileClasspath'.
> Could not find support-fragment.aar (com.android.support:support-fragment:27.1.1).
  Searched in the following locations:
      https://jcenter.bintray.com/com/android/support/support-fragment/27.1.1/support-fragment-27.1.1.aar
> Could not find support-core-ui.aar (com.android.support:support-core-ui:27.1.1).
  Searched in the following locations:
      https://jcenter.bintray.com/com/android/support/support-core-ui/27.1.1/support-core-ui-27.1.1.aar

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

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

BUILD FAILED in 23s
14 actionable tasks: 1 executed, 13 up-to-date

Please suggest me some solution for this

@obsverable makes the starter kit crash

Describe the bug
Using the @observable decorator, makes the starter kit crashes on release mode only. It works when we are in debug mode.

The problem came from the last update of React-native 0.56.0 where they introduced the new babel@7 into the core of the framework. It's a matter of babel-helpers that are not imported into react-native and makes it crashs. You can follow the issue here facebook/react-native#20150

To Reproduce

export default class Home extends React.Component<IReactNavigation> {

+ @observable
+ isLoaded = false;

static get options() {
  return {
    topBar: {
      title: {
        text: 'Home',
      },
    },
  };
}

Screenshots

2018-09-28 10:47:56.703 react-native-starter[25023:6977768] [error][tid:com.facebook.react.JavaScript] babelHelpers.applyDecoratedDescriptor is not a function. (In 'babelHelpers.applyDecoratedDescriptor(n.prototype,"isLoaded",[b.observable],{configurable:!0,enumerable:!0,writable:!0,initializer:function(){return!1}})', 'babelHelpers.applyDecoratedDescriptor' is undefined)

Environment

  • React Native Starter version: 2.0.0
  • React Native version: 0.57.0
  • Platforms
    • iOS
    • Android
  • Device Info
    • Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

bug RCTText

I think you should upgrade react-native version to 0.53.3
I've got problems with RCTText component with version 0.53.0

Detox okhttp3 version constraint conflicts on release build

Get below errors on release build in the :detox:complileMinReactNative46DebugRenderscript task

Seem harmless can still run app though.

Caused by: org.gradle.api.GradleException: Cannot find a version of 'com.squareup.okhttp3:okhttp' that satisfies the version constraints: 
   Dependency path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp:3.6.0'
   Constraint path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp' strictly '3.6.0' because of the following reason: minReactNative46DebugRuntimeClasspath uses version 3.6.0
   Dependency path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp:3.6.0'
   Constraint path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp' strictly '3.6.0' because of the following reason: minReactNative46DebugRuntimeClasspath uses version 3.6.0
   Dependency path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp:3.6.0'
   Constraint path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp' strictly '3.6.0' because of the following reason: minReactNative46DebugRuntimeClasspath uses version 3.6.0
   Dependency path 'passfolio:detox:unspecified' --> 'com.squareup.okhttp3:okhttp:3.6.0'
   Dependency path 'passfolio:detox:unspecified' --> 'com.facebook.react:react-native:0.57.4' --> 'com.squareup.okhttp3:okhttp:3.11.0'
   Dependency path 'passfolio:detox:unspecified' --> 'com.facebook.react:react-native:0.57.4' --> 'com.facebook.fresco:imagepipeline-okhttp3:1.10.0' --> 'com.squareup.okhttp3:okhttp:3.10.0'
   Dependency path 'passfolio:detox:unspecified' --> 'com.facebook.react:react-native:0.57.4' --> 'com.squareup.okhttp3:okhttp-urlconnection:3.11.0' --> 'com.squareup.okhttp3:okhttp:3.11.0'

react-native run-ios CFBundleIdentifier Does Not Exist issue

FYI I had to modify my Workspace Build System settings to successfully run react-native run-ios. Was seeing the following issue.

An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=2):
Failed to install the requested application
An application bundle was not found at the provided path.
Provide a valid path to the desired application bundle.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/foundation.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist


Error: Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/foundation.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

    at checkExecSyncError (child_process.js:575:11)
    at Object.execFileSync (child_process.js:593:13)
    at Promise.then (/Users/dwhitehead/Documents/github/react-native-starter/node_modules/react-native/local-cli/runIOS/runIOS.js:208:5)
    at <anonymous>

Resolved it by doing the following
screen shot 2018-11-23 at 09 26 26

screen shot 2018-11-23 at 09 26 43

react-native info

    System:
      OS: macOS 10.14.1
      CPU: x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
      Memory: 301.08 MB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 9.7.1 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
      Android SDK:
        Build Tools: 23.0.1, 25.0.3, 26.0.1, 26.0.2, 27.0.1, 27.0.3, 28.0.2, 28.0.3
        API Levels: 23, 26, 27, 28
    IDEs:
      Android Studio: 3.1 AI-173.4720617
      Xcode: 10.1/10B61 - /usr/bin/xcodebuild
    npmPackages:
      @types/react: 16.4.14 => 16.4.14
      @types/react-native: 0.57.1 => 0.57.1
      react: 16.5.2 => 16.5.2
      react-native: 0.57.2 => 0.57.2

Not sure how you want to update the documentation or repo to prevent this in the future, but happy to help if you'd like.

Is this project compatible with react-native-fetch-blob?

This might be a more general cocoapods issue, but I've tried to install the very popular react-native-fetch-blob package, and dependencies don't appear to be shared into that codebase, despite their having a podspec.

What else needs to be done? Is this a header search paths issue? Is it necessary to somehow patch dependencies that do have podspecs as well?

Combine models

Describe the bug
I'm not really clear, I think it is an issue of how I use mobx, but I just wanted to have your opinion on the models structure.
I have a UI model from the boilerplate for all the ui updates. Can I combine it with other models that I want to implement like LOGIN, USER, etc.
I get a weird behaviour when I do the following:

import { AsyncStorage } from "react-native";
import { types, flow, onSnapshot } from "mobx-state-tree";
import makeInspectable from "mobx-devtools-mst";

import { UI } from "./models/UI";
import { LOGIN } from "./models/LOGIN";
import debounce from "lodash/debounce";

export const Store = types
  .model("Store", {
    UI,
    LOGIN,
    isHydrated: false
  })
  .actions(self => ({
    hydrate: flow(function* hydrate() {
      yield self.UI.hydrate();
      yield self.LOGIN.hydrate();
      self.isHydrated = true;
    })
  }))
  .create({
    UI: {},
    LOGIN: {}
  });

// Persist snapshots
onSnapshot(
  Store.UI,
  debounce(
    snapshot => AsyncStorage.setItem("UI", JSON.stringify(snapshot)),
    1000
  )
);

onSnapshot(
  Store.LOGIN,
  debounce(
    snapshot => AsyncStorage.setItem("LOGIN", JSON.stringify(snapshot)),
    1000
  )
);

if (__DEV__) {
  makeInspectable(Store.UI);
  makeInspectable(Store.LOGIN);
}

My Login model:

import { AsyncStorage } from 'react-native';
import { types, flow, applySnapshot } from 'mobx-state-tree';

export const LOGIN = types.model('LOGIN', {
    token: types.optional(types.string, ''),
    fetching: types.optional(types.boolean, false),
    error: types.optional(types.boolean, false)
  })
  .actions(self => ({
    login(username?: string, password?: string) {
      if (username && password) {
        
      }
    },
    logout() {
      
    },
    hydrate: flow(function* () {
      const data = yield AsyncStorage.getItem('LOGIN');
      if (data) {
        applySnapshot(self, JSON.parse(data));
      }
    }),
  }))
  .views(self => ({
    get token() {
      return self.token
    },
    get isFetching() {
      return self.fetching
    },
    get error() {
      return self.error
    }
  }));

Expected behavior
Should initialize models just fine.

Screenshots
If applicable, add screenshots or a video to help explain your problem.

image

Environment

  • React Native Starter version: [2.0.0]
  • React Native version: [0.57.8]
  • Platforms
    • iOS
    • Android
  • Device Info
    • Physical Device in Debug
    • Physical Device in Release
    • Simulator in Debug
    • Simulator in Release

Additional context

Run react-native info in your terminal and paste its contents here.
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
Memory: 65.14 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.6.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 22, 23, 24, 25, 26, 27
Build Tools: 23.0.1, 23.0.2, 23.0.3, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.1, 26.0.2, 27.0.0, 27.0.1, 27.0.2, 27.0.3
IDEs:
Android Studio: 3.1 AI-173.4907809
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.7.0 => 16.7.0
react-native: 0.57.8 => 0.57.8
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

unneeded postinstall.sh command?

Reset version on rename

We should add a feature to reset version numbers to the rename script.

Also in package.json

'-f was unexpected at this time' on prepare script (yarn postinstall)

Describe the bug
When installing react-native-starter as described below on Windows 10, the following error is outputted:

Error: Command failed: npm run prepare
-f was unexpected at this time.
npm ERR! errno 1
npm ERR! [email protected] prepare: `patch-package && if [ -f ./scripts/postinstall.sh ]; then sh ./scripts/postinstall.sh; fi`

To Reproduce
Steps to reproduce the behavior:

  1. From fresh: clone, cd to app
  2. yarn

Expected behavior
App's dependencies install as expected with no errors

Debug log

λ yarn
yarn install v1.9.4
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @react-native-community/[email protected]" has incorrect peer dependency "react-native@^0.57.0".
warning " > [email protected]" has incorrect peer dependency "mobx@^2.2.0 || ^3.0.0".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning "react-native > @react-native-community/[email protected]" has incorrect peer dependency "react-native@^0.57.0".
warning "react-native > metro-react-native-babel-transformer > babel-preset-fbjs > @babel/[email protected]" has incorrect peer dependency "@babel/[email protected]".
[4/4] Building fresh packages...
[6/9] ⠈ electron
[7/9] ⠈ node-sass
[-/9] ⠈ waiting...
[4/9] ⠈ dtrace-provider
error X:\path\to\app\node_modules\postinstall-prepare: Command failed.
Exit code: 1
Command: node ./run.js
Arguments:
Directory: X:\path\to\app\node_modules\postinstall-prepare
Output:
-f was unexpected at this time.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] prepare: `patch-package && if [ -f ./scripts/postinstall.sh ]; then sh ./scripts/postinstall.sh; fi`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     Z:\path\to\user\AppData\Roaming\npm-cache\_logs\2019-06-14T23_20_20_987Z-debug.log
child_process.js:645
    throw err;
    ^

Error: Command failed: npm run prepare
-f was unexpected at this time.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] prepare: `patch-package && if [ -f ./scripts/postinstall.sh ]; then sh ./scripts/postinstall.sh; fi`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     Z:\path\to\user\AppData\Roaming\npm-cache\_logs\2019-06-14T23_20_20_987Z-debug.log

    at checkExecSyncError (child_process.js:602:13)
    at execSync (child_process.js:642:13)
    at Object.<anonymous> (X:\path\to\app\node_modules\postinstall-prepare\run.js:14:5)
    at Module._compile (module.js:653:30)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)

Environment

This is a fresh install so versions don't really matter

  • React Native Starter version: 2.1.0
  • Platforms
    • Windows 10 latest

Additional context

λ react-native info
info
  React Native Environment Info:
    System:
      OS: Windows 10
      CPU: x64 AMD Ryzen 5 1600 Six-Core Processor
      Memory: 5.34 GB / 15.95 GB
    Binaries:
      Yarn: 1.9.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
      npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

λ react-native -v
react-native-cli: 2.0.1
react-native: 0.59.0-rc.3

Example of how to wire up Mobx State Tree with React Native Firebase (Cloud Firestore)

Is your feature request related to a problem? Please describe.
Not a problem per se, but rather a request for an example on how to (good practice) wire up mobx-state-tree with react-native-firebase.

Describe the solution you'd like
A medium complexity example that illustrates data syncing with Cloud Firestore.

Describe alternatives you've considered
I'm learning both MST and RN Firebase and I will eventually provide an example if I can, but I'm not there yet!

Additional context
None at the moment.

xcodebuild on AppCenter not seeing env vars

xcodebuild invoked by AppCenter doesn't seem to find environment variables set on AppCenter's Build UI page.

Specifically, Xcode can't seem to find env variable SENTRY_AUTH_TOKEN, which is used in Bundle React Native code and images step. Is there any way I can get a hold of it in the xcodebuild process?

To Reproduce
Steps to reproduce the behavior:

  1. When iOS build comes into Bundle React Native code and images step, this piece of code is not executed (because SENTRY_AUTH_TOKEN is not set):
if [ ! -z "$SENTRY_AUTH_TOKEN" ]; then
../node_modules/@sentry/cli/bin/sentry-cli react-native xcode ../node_modules/react-native/scripts/react-native-xcode.sh
else

Expected behavior
I would expect xcodebuild for it to pick it up. "works on my machine" :)

Environment

  • React Native Starter version: 2.0.0
  • React Native version: 0.57

Documentation

Create next steps guide

  • Add guide how to rename the app and change bundle identifiers
  • How to add icons for iOS and Android
  • FAQ and troubleshooting

XMLHttpRequest global replacement

In src/index.js line 26 we have this line:

XMLHttpRequest = GLOBAL.originalXMLHttpRequest || GLOBAL.XMLHttpRequest;

This is super awesome for seeing Network requests in the Chrome developer tools! But it breaks uploading multipart images with the dev tools open. For some reason the body becomes [Object object] and the content-type then becomes text/plain.

Perhaps this should be commented out, or enabled under a different flag than __DEV__ - I don't think this should be the default behaviour as it was super hard to track down what was causing it :(

Update existing project

How do you update a currently existing react-native-starter project to the latest version of the boilerplate or at least merge changes.

Deep linking support?

Hi there, I previously commented on an open issue so you might remember my face! I've decided to take the plunge and am using this starter kit as the launching point for my first RN build. So far I am really enjoying the codebase and the opinionated decisions that have been made.

I'm new to RN, so you'll have to excuse me if I'm missing something very obvious, but it looks like this starter kit does not support any kind of deep linking out of the box, is that right?

Of course, react-native-navigation has its own setOnNavigatorEvent for deep linking, but out of the box I can't see a way to actually add a linking scheme to this ueno kit.

If that's correct, I'll proceed manually with react-native-deep-linking (or similar). Might be worth opening a feature request, as I imagine almost all RN projects need this.

fastlane tag_version failed in App Center Build

Related logs as below:

[10:04:20]: ▸ [35mfatal: could not read Password for 'https://***@dev.azure.com': Device not configured[0m
+----------------------+---------------------+
| [33mLane Context[0m |
+----------------------+---------------------+
| DEFAULT_PLATFORM | android |
| PLATFORM_NAME | android |
| LANE_NAME | android tag_version |
| ANDROID_VERSION_NAME | 1.0.1 |
| ANDROID_VERSION_CODE | 2 |
+----------------------+---------------------+

Unable to find a specification for `boost-for-react-native` depended upon by `Folly`

Describe the bug
yarn install error:

[!] Unable to find a specification for `boost-for-react-native` depended upon by `Folly`

To Reproduce
Steps to reproduce the behavior:

  1. hub clone eno-llc/react-native-starter
  2. cd react-native-starter
  3. yarn install
  4. See error

Environment

  • React Native Starter version: develop

Additional context

React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
      Memory: 4.96 GB / 16.00 GB
      Shell: 5.5.1 - /usr/local/bin/zsh
    Binaries:
      Node: 8.11.0 - ~/.nvm/versions/node/v8.11.0/bin/node
      Yarn: 1.9.4 - ~/.nvm/versions/node/v8.11.0/bin/yarn
      npm: 6.3.0 - ~/.nvm/versions/node/v8.11.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3
      Android SDK:
        Build Tools: 20.0.0, 21.1.2, 22.0.1, 23.0.1, 23.0.3, 24.0.3, 25.0.0, 25.0.3, 26.0.2, 26.0.3, 27.0.3
        API Levels: 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27
    IDEs:
      Android Studio: 3.1 AI-173.4720617
      Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild
    npmPackages:
      @types/react: 16.4.13 => 16.4.13
      @types/react-native: 0.56.17 => 0.56.17
      react: 16.5.0 => 16.5.0
      react-native: 0.57.0-rc.4 => 0.57.0-rc.4
    npmGlobalPackages:
      react-native-cli: 2.0.1

./scripts/rename.sh: line 108: ./scripts/build-env.sh: No such file or directory

Describe the bug
init project from ueno-app native fail

To Reproduce
Steps to reproduce the behavior:
1 clone or init ueno-app from yarn create always have error: ./scripts/rename.sh: line 108: ./scripts/build-env.sh: No such file or directory

in rename step.

Expected behavior
just wanna create a project from ueno-app react native starter

Screenshots
If applicable, add screenshots or a video to help explain your problem.

Environment

  • React Native Starter version: lastest version (5/2/2020)
  • React Native version: 0.62.0-rc1

Additional context

I think this bug is very clear. when i check line 108 in ./scripts/rename.sh. this line invoke a file that doesn't exist.
Please check out and fix this. I love this project so much, but not have enough knowledge in react native and nativ to pull request and fix right now.

Error with babel on signed Android APK

I don't know if this is a problem with my code, but looking around the internet, turn out this is a problem regarding babel. I keep getting

TypeError: undefined is not a function (evaluating 'babelHelpers.objectDestructuringEmpty(e)') on one of my screens, and only that screen. I have checked the code multiple times, and didn't find any type of code that would raise such error. Many suggested removing the .babelrc file, but didn't help at all.

Upgrade to react-native-navigation v2?

So it seems like react-native-navigation v2 is finally stable enough to be officially recommended by the maintainers.

Just wondering if a PR to upgrade this repo to v2 would be accepted.

Installing library error: 'React/RCTBridgeModule.h' file not found

First of all, please accept my apology if this post belongs on StackOverflow or some other sort of help forum instead of here. I am new to RN so I am unaware if this problem lies in my own ignorance, or some configuration of this starter kit. If the maintainers feel this issue is not appropriate here please do close it.

I am attempting to install react-native-share-extension into a clone of this repo. After following their setup instructions exactly, I receive the following error:

my-app/node_modules/react-native-share-extension/ios/ReactNativeShareExtension.h:2:9: fatal error: 'React/RCTBridgeModule.h' file not found

I've spent quite some hours looking into this already. I notice you import this RCTBridgeModule in ios/react-native-starter/RNUeno.h. What is the purpose of this? Is this related, or actually unrelated?

I am aware of the section in the docs here on adding dependencies, although I'm not 100% sure it applies in this case. I've added a podspec to the above repo, making sure to detail React as a dependency. This has no effect on the above error.

In short, is there something special I need to do due to the structure of this starter kit?

Bitrise.yml

It would be great to see how you have bitrise configured.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.