Version 3.3.85 of react-native-ui-lib was just published.

The version 3.3.85 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-ui-lib.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.3.51 of react-native-ui-lib was just published.

The version 3.3.51 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-ui-lib.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.408 of react-native-navigation was just published.

The version 1.1.408 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-navigation.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.441 of react-native-navigation was just published.

The version 1.1.441 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-navigation.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 3.3.33 of react-native-ui-lib was just published.

The version 3.3.33 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-ui-lib.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

Version 0.55.15 of @types/react-native was just published.

The version 0.55.15 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of @types/react-native.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

Version 1.1.463 of react-native-navigation was just published.

The version 1.1.463 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-navigation.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.55.2 of @types/react-native was just published.

The version 0.55.2 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of @types/react-native.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.1.398 of react-native-navigation was just published.

The version 1.1.398 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of react-native-navigation.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

Version 16.3.15 of @types/react was just published.

The version 16.3.15 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of @types/react.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

Your Greenkeeper bot :palm_tree:

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! react-native-starter[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 "[email protected]^0.57.0".
warning " > [email protected]" has incorrect peer dependency "[email protected]^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 "[email protected]^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
  • [x] 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

Describe the bug

Attempting to npm run android gives the following error message (extra newlines added for readability)

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:processDebugResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > Android resource linking failed
     /Users/xyz/projects/typescript-react-native-starter/android/app/src/main/res/values/strings.xml: 
AAPT: error: resource string/ANDROID_CODEPUSH_DEPLOYMENT_KEY (aka com.xyz.typescriptreactnativestarter:string/ANDROID_CODEPUSH_DEPLOYMENT_KEY) 
not found.

To Reproduce Steps to reproduce the behavior:

1. Clone repo
2. Install dependencies
3. Commented out all firebase references in gradle files (not sure if relevant, I did this to get passed the missing google-services.json error)
4. npm run android

Expected behavior Should see emulator and app without error.

Notes I haven't set any of the environment variables in .env.public. The instructions didn't mention them (are they required?) and I wouldn't know what values to set them to anyways. I'm not familiar with AppCenter or CodePush.

Environment

• React Native Starter version: 3.0.0-alpha.0
• React Native version: 0.62.0
• Platforms
  • [ ] iOS
  • [X] Android
• Device Info
  • [ ] Physical Device in Debug
  • [ ] Physical Device in Release
  • [X] Simulator in Debug
  • [ ] Simulator in Release

Additional context

Run react-native info in your terminal and paste its contents here.

System: OS: macOS 10.15.4 CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz Memory: 146.02 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 12.17.0 - ~/.nvm/versions/node/v12.17.0/bin/node Yarn: Not Found npm: 6.14.4 - ~/.nvm/versions/node/v12.17.0/bin/npm Watchman: Not Found Managers: CocoaPods: Not Found SDKs: iOS SDK: Not Found Android SDK: API Levels: 26, 28, 29 Build Tools: 28.0.3, 29.0.3 System Images: android-26 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom_64 Android NDK: Not Found IDEs: Android Studio: 3.6 AI-192.7142.36.36.6392135 Xcode: /undefined - /usr/bin/xcodebuild Languages: Java: 1.8.0_252 - /usr/bin/javac Python: 2.7.16 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.62.0 => 0.62.0 npmGlobalPackages: react-native: Not Found

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
  • [X] Android
• Device Info
  • [ ] Physical Device in Debug
  • [ ] Physical Device in Release
  • [X] 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