[WIP] Adds minimal boilerplate

[DevanB]

Please test to verify all is working!

[DevanB]

@marktani

This error is nasty and really should be handled in a more graceful way, but is being debated over in the react-apollo ticket (#604)

In the meantime, it seems you didn't have the server running.

This leads me to propose that we make sure the start script starts up possibly nodemon to start up the Expo packager and the server.

Thoughts?

[marktani]

I definitely had the server running, but I can't say if I started the app first. Is that a problem?

[DevanB]

Did you possibly start the server after seeing the error? I can reproduce the error by:

1. Starting the Expo packager (yarn start)
2. Opening the iOS simulator
3. See the error

Then I can fix it by:

1. Starting the server (yarn start in the server directory)
2. Pressing Reload (or command + R in the simulator)

On Jan 13, 2018, at 6:51 AM, Nilan Marktanner [email protected] wrote:

I definitely had the server running, but I can't say if I started the app first. Is that a problem?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/graphql-boilerplates/react-native-fullstack-graphql/pull/72#issuecomment-357429244, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVpXEoe9tY1sj7TtvOTPEBqUe0cTh2Cks5tKJi2gaJpZM4RVtNd.

[marktani]

Thanks I'll try that again 🙂

For the record, I am using a real Android device, if that makes a difference.

[DevanB]

Nope, you should still see the same errors I was seeing!

We should maintain this repo in the manner that we assume any user is using either/or iOS and/or Android

:)

On Jan 13, 2018, at 6:54 AM, Nilan Marktanner [email protected] wrote:

Thanks I'll try that again 🙂

For the record, I am using a real Android device, if that makes a change.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/graphql-boilerplates/react-native-fullstack-graphql/pull/72#issuecomment-357429385, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVpXFw_l6tPjYO7j__FoTv7-ELtiUE7ks5tKJlcgaJpZM4RVtNd.

[DevanB]

Hmm, updated the Expo and the server locally tonight, and am seeing the same problem again. I now know that the problem is a network error, but haven't tracked down why the ApolloClient can't talk with the server when they are both running...