hsunami10 / ldr-app-client Goto Github PK

Java 0.56% JavaScript 97.42% Objective-C 1.10% Ruby 0.44% Starlark 0.49%

ldr-app-client's Introduction

Setup Instructions

yarn start
react-native run-ios

If you see -bash: react-native: command not found, install it globally using npm install --location=global react-native-cli.

Troubleshooting

yarn start - watchman crawl failed If you get this error:

Loading dependency graph...jest-haste-map: Watchman crawl failed. Retrying once with node crawler.
  Usually this happens when watchman isn't running. Create an empty `.watchmanconfig` file in your project's root folder or initialize a git or hg repository in your project.
  Error: Watchman error: std::__1::system_error: open: /Users/michaelhsu/Documents/GitHub/LDR-App-client: Operation not permitted. Make sure watchman is running for this project. See https://facebook.github.io/watchman/docs/troubleshooting.html.
 ERROR  std::__1::system_error: open: /Users/michaelhsu/Documents/GitHub/LDR-App-client: Operation not permitted
error Command failed with exit code 11.

Per this link, try running:

watchman watch-del-all
watchman shutdown-server

yarn start - failed to construct transformer Failed to construct transformer: Error: error:0308010C:digital envelope routines::unsupported Try downgrading Node.js to a previous version. The version that works for me is v12.3.0.

xcrun instruments error

xcrun: error: unable to find utility "instruments", not a developer tool or in PATH

Command failed: xcrun instruments -s
xcrun: error: sh -c '/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -find instruments 2> /dev/null' failed with exit code 17664: (null) (errno=Invalid argument)
xcrun: error: unable to find utility "instruments", not a developer tool or in PATH

Solution: check if XCode command line tools are installed. If yes, then try upgrading to the latest version of react-native with yarn upgrade react-native@latest or at least v0.64.0.

This may cause the error below, please read further.

react-native run-ios: build failed

fatal error: 'React/RCTBridgeModule.h' file not found
#import <React/RCTBridgeModule.h>
        ^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

Solution: cd into the /ios directory and try running pod install.

pod install error: CocoaPods could not find compatible versions

[!] CocoaPods could not find compatible versions for pod "React/RCTVibration":
  In snapshot (Podfile.lock):
    React/RCTVibration (from `../node_modules/react-native`)

  In Podfile:
    React/RCTVibration (from `../node_modules/react-native`)

None of your spec sources contain a spec satisfying the dependency: `React/RCTVibration (from `../node_modules/react-native`)`.

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.

No viable solution yet...

ldr-app-client's People

Contributors

Watchers

ldr-app-client's Issues

implement searchable header

with animated text input on active

use AppState to handle different notifications

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

check if everything exists before querying, handle these "do not exist" errors, correctly handle all types of errors

when logging in / signing up, store into keychain

iOS swiping back gesture bug?

Swiping back with
static navigationOptions = { gesturesEnabled: false }
goes to the AuthLoadingScreen. Why is this?

how to correct use redux state

If the data should be consistent across ALL SCREENS, not just one, then store it globally in redux state. Otherwise, if it is different across screens, store it in screens.

handle loading and showing an alert bug

When the user performs an AJAX request and the app state is set to "loading", and the requests finishes and the app state is set to "not loading" and an alert is shown, the alert closes automatically and the loading hangs