Create-react-native-app: Certificate for this server is invalid

Created on 6 Jun 2017  ยท  6Comments  ยท  Source: expo/create-react-native-app

Description

I run create-react-native-app and then yarn run ios on my local machine and get an error in iOS simulator

There was a problem loading the experience
Error while loading: The certificate for this server is invalid. You might be connecting to a server that is pretending to be "exp.host" which could put your confidential information at risk.." (code -1202)

Expected Behavior

Expected local create-react-native-app to run in iOS Simulator.

Observed Behavior

screen shot 2017-06-06 at 9 47 30 am

Environment

Please run these commands in the project folder and fill in their results:

  • npm ls react-native-scripts:
npm ls react-native-scripts
[email protected] /Users/byn998/dev/crna-cert-test
โ”œโ”€โ”€ UNMET PEER DEPENDENCY [email protected]
โ””โ”€โ”€ [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
  • npm ls react-native:
npm ls react-native
[email protected] /Users/byn998/dev/crna-cert-test
โ”œโ”€โ”€ UNMET PEER DEPENDENCY [email protected]
โ””โ”€โ”€ [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
  • npm ls expo:
 npm ls expo
[email protected] /Users/byn998/dev/crna-cert-test
โ”œโ”€โ”ฌ [email protected]
โ”‚ โ””โ”€โ”€ UNMET PEER DEPENDENCY react@>=15.3.1
โ””โ”€โ”€ UNMET PEER DEPENDENCY [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
npm ERR! peer dep missing: react@>=15.3.1, required by [email protected]
npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
  • node -v:
node -v
v8.0.0
  • npm -v:
npm -v
4.2.0
  • yarn --version:
yarn --version
0.24.6
  • watchman version:
watchman version
{
    "version": "4.7.0"
}

Also specify:

  1. Operating system: macOS Sierra version 10.12.5
  2. Phone/emulator/simulator & version: Xcode 8.3.2 (8E2002), simulator iPhone 7 - iOS 10.2 (143269)

Reproducible Demo

Cloned, installed and tested using a fresh create-react-native-app following instructions. Looking for any assistance to fix this. Might be a configuration problem on my machine, and not a CRNA bug, but I don't know.

networking underlying tools

All 6 comments

Hello! This looks like a problem with your network connection. Were you on a public wifi network? Try Reseting your Simulator and your computer. If that doesn't fix it, let me know more information about what wifi network you're on and whether you get this same warning when you go to https://exp.host/ in your browser

Hey Brent! I'm on my work network. When I go to expo.host in my browser it takes me to the Expo webpage.

We have a proxy for our work network. Maybe create-react-app and/or iOS Simulator isn't honoring my shell's proxy configurations with ALL_PROXY, HTTPS_PROXY, and HTTP_PROXY shell config vars?

Thanks!

Ok, new info: I opened exp.host in my Safari on the iOS Simulator. I get a certificate exception, and it shows the incorrect certificate that my network is serving because it is blocked. Seems to be blocked only because the iOS Simulator is not respecting my proxy tunnel. If the simulator were to use the proxy tunnel I have set in my Network prefs, and shell vars, the exp.host would work as it does in my browsers on desktop. Will report back if I find a solution. If you have any ideas for me to try to debug, or fix, let me know, otherwise don't sweat it. Thanks for your help my man

Apparently you need to reset the simulator between proxy changes, but that's I think all that I know.

For posterity: I found this Stack Overflow q/a https://stackoverflow.com/questions/25439756/how-to-use-charles-proxy-on-the-xcode-6-ios-8-simulator that lead me to this proxy app called Charles that has a section on proxying, and installing certs for iOS Simulator https://www.charlesproxy.com/documentation/faqs/ssl-connections-from-within-iphone-applications/

Trying this now!

Just letting you know that we had the same issue on the IOS Simulator (node 6.4.0, npm 4.2.0).
Fixed via your _reset content and settings_ advice. -a-

Was this page helpful?
0 / 5 - 0 ratings

Related issues

ArashMotamedi picture ArashMotamedi  ยท  3Comments

scf4 picture scf4  ยท  5Comments

jckuhl picture jckuhl  ยท  4Comments

iRoachie picture iRoachie  ยท  5Comments

anp picture anp  ยท  3Comments