Unable to make API calls using react-native

Question

I have a VM running locally that's built using Vagrant. I am able to curl and go to the URL directly from the browser. For some reason, when I make the same call in my react-native app using the fetch API, it keeps giving me the Network request failed error.

Here is a snippet of the code:

fetchData() {

  this.setState({ isLoading: true });

  var baseURL = 'https://192.168.33.33/api/session';

  console.log('URL: >>> ' + baseURL);

  fetch(baseURL)
  .then((response) => response.json())
  .then((responseData) => {
    console.log(responseData);
  })
  .catch(error => {
    console.log(error);
  })
  .done();
}

The baseURL log there returns the right URL and the error looks like so:

URL: >>> http://192.168.33.33/api/session
TypeError: Network request failed {stack: (...), message: "Network request failed"}
  message: "Network request failed"
  stack: (...)
  get stack: function () { [native code] }
  set stack: function () { [native code] }
  __proto__: Error

I thought it might've been an issue with my VM not being accessible somehow by my app, so I went ahead and deployed it to a real server and it still gave the same error.

Any ideas?

does `https://192.168.33.33/api/session` maybe require some kind of headers on your get request? — lyjackal, May 26 '15 at 06:29
@lyjackal I don't think so, all the code does is this: http://d.pr/n/18BiU/3kXPWHcD — Koes Bong, May 26 '15 at 14:54
If you use the XMLHttpRequest object instead of fetch, do you get the same error? Is CORS setup correctly? — user2943490, Jun 01 '15 at 07:02
Can you provide us with the URL of your real server so that we can possibly reproduce the error? — ljk321, Jun 02 '15 at 08:27

score 4 · Accepted Answer · answered Jun 04 '15 at 14:19

Found the problem and solved it.

The issue was caused by having self-signed certificate in the API server without a self created CA.

I could try creating my own CA and then create a certificate from that but I went ahead and got a cheap real SSL cert. That solved the issue.

score -1 · Answer 2 · edited May 23 '17 at 11:59

-1

I think you might be facing the same origin policy constraint.

There are many ways of workaround it.

edited May 23 '17 at 11:59

Community

1
1

answered Jun 02 '15 at 21:49

Christian

7,062
9
53
79

Thanks for your answer! unfortunately, that wasn't the case. – Koes Bong Jun 04 '15 at 21:23
2

This doesn't apply to react native apps. – Clintm Apr 14 '16 at 14:36
same origin policy is only for the browser! – Germinate Sep 06 '17 at 02:43

Unable to make API calls using react-native

2 Answers2

Linked