Fetch not working on Android 9 API 28 #24627

mttrthomazelli · 2019-04-26T16:02:16Z

🐛 Bug Report

Hello,

I'm having an Issue about a HTTP service (the error only in simulator with API 28 (Pie) environment). I already add the domain on react_native_config.xml and add the networkSecurityConfig on both Manifests.xml (debug and release) but still get the TypeError: Network request failed error:

I already try all this Issues: #23986, #23984

My info:
info
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (8) x64 Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz
Memory: 318.58 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.8.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 25, 26, 27, 28
Build Tools: 25.0.0, 25.0.1, 26.0.2, 27.0.3, 28.0.3
System Images: android-25 | Google APIs Intel x86 Atom, android-25 | Google APIs Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5199772
Xcode: 10.2/10P91b - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.0 => 0.59.0
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7

My react_native_config.xml:

acolhebrasil.com.br

localhost 10.0.2.2 10.0.3.2

My fetch:
fetch(baseURLAPI + action, {
method: method,
headers: headers,
body: bodyObj ? JSON.stringify(bodyObj) : null
}).then((response) => {
console.log(response)
if(response.ok){
return response.json();
}
throw new Error(response.text());
})
.then((responseJson) => {
console.log(responseJson)
if(callbackSuccess){
return callbackSuccess(responseJson);
}
})
.catch((error) => {
console.log(error)
if(callbackError){
return callbackError(error);
}
});
My API: http://acolhebrasil.com.br/Sistema/api/#/

Console:
TypeError: Network request failed
at XMLHttpRequest.xhr.onerror (ReactNativeRenderer-dev.js:3731)
at XMLHttpRequest.dispatchEvent (ReactNativeRenderer-dev.js:10394)
at XMLHttpRequest.setReadyState (ReactNativeRenderer-dev.js:10127)
at XMLHttpRequest.__didCompleteResponse (ReactNativeRenderer-dev.js:9895)
at ReactNativeRenderer-dev.js:10051
at RCTDeviceEventEmitter.emit (blob:http://localhost:8081/9854a9b9-407d-4571-8675-e6fadd170803:3282)
at MessageQueue.__callFunction (ReactNativeART.js:13)
at blob:http://localhost:8081/9854a9b9-407d-4571-8675-e6fadd170803:2336
at MessageQueue.__guard (ReactNativeART.js:10)
at MessageQueue.callFunctionReturnFlushedQueue (blob:http://localhost:8081/9854a9b9-407d-4571-8675-e6fadd170803:2335)

andresmtz98 · 2019-04-26T16:31:08Z

Same here. There is an exception called "NoSuchKeyException" when use fetch api (it's only as release).

mttrthomazelli · 2019-04-26T18:05:53Z

I tried now to change fetch to axios, same error. I believe that is an Android security configuration missing ou somenthing like.

andresmtz98 · 2019-04-26T18:12:37Z

I tried now to change fetch to axios, same error. I believe that is an Android security configuration missing ou somenthing like.

It seems that the solution for now is to rollback my RN project (from last version .59.5) to .58 :/, but i'm using hooks :(

0xDub · 2019-04-29T10:32:23Z

Same issue here, have you found any better solutions by any chance? I'm running RN 0.58.3 for reference

andresmtz98 · 2019-04-29T17:45:19Z

See this #24361

codypearce · 2019-04-30T20:27:22Z

Same here on 0.58.6.

I have tried network_security_config.xml as described here #22375
As well as a android:usesCleartextTraffic="true" as described here #23986
Also tried axios
Still getting the same error

I use http://localhost:5000 for the local api.

hey99xx · 2019-05-01T06:34:33Z

On latest RN 0.59.x, all http connections should be doable in debug apps, and https should only be enforced in release apps.

If issue is related to network_security_config, using XMLHttpRequest/fetch/axios won't matter.
They will all go through RN's networking native module, which uses OkHttp that checks if Android app allows insecure connections and will be blocked there.

I don't know about NoSuchKeyException related to this, please copy paste an entire stack trace.

Also version numbers reported here by multiple people are conflicting, please clearly write
- what RN version (0.57, 0.58, 0.59) you're testing with, preferably with minor releases like 0.59.0, 0.59.1 etc.
- if you use debug vs release apks
- Android API version
to better understand what the issue is and possibly find a culprit in commit history quicker.

mrkacan · 2019-05-02T12:15:09Z

You need to use "https" when fetching something. Installing SSL certificate and enabling https link solved my issue. (I did try Android 9.0, axios is working, fetch is working.)

codypearce · 2019-05-02T14:01:10Z

@mrkacan Many people use localhost for their api in development and many also do not have their localhost setup with https yet. I think this is a common enough use case that it should be supported.

zhigang1992 · 2019-05-07T09:06:31Z

Are you able to access the api from chrome browser? localhost on Android emulator is not the same as the host. You might need to do a adb reverse for it to work

mohsenomidi · 2019-05-07T11:16:08Z

Hi
same issue here!

for testing purposes, we are using http for fetch data to our test physical mobile devices, if react-native block this capability, in our test environments we should install more than one ssl certificate and it made complex routines for internal tests.
i completely agree for security reasons in production environment the users must use https, but the liability shift will not take by development languages it should not force the devopers to use single security option, for example, if some programming languages declined the udp connection beacuse it is not reliable for some reasons, it will not be acceptable.

it doesn't make sense to prevent using http in development level, some use cases and some business may use http, without any security becase the net work is private and ssl encapsulation will made the request/response too slow.

i think this rule must be add in devoploment and business level not in development languages level.

Regards.

mohsenomidi · 2019-05-14T09:22:47Z

Hi All,

I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml

<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

mmihic96 · 2019-06-03T09:30:07Z

@mohsenomidi
Thank You very much. That worked for me!

igorserafim · 2019-06-07T19:58:37Z

Hi All,

I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml

<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

That worked for me too. Thanks! @mohsenomidi

I was having the same problem OP had, but using axios and having just updated my cordova android platform to the newest one.

mathosmor · 2019-06-12T16:21:09Z

@mohsenomidi That worked for me too :)

hohien · 2019-06-14T07:29:57Z

@mohsenomidi You save my life today, Thanks

MobileDevStar · 2019-06-20T08:29:13Z

Thanks for your help

Hi All,

I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml

<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

amohit1315 · 2019-06-21T15:23:37Z

is the issue solved for https??

Trying to fetch data from remote server via api.
Using fetch(https:url:port) to fetch the data. But every time android emulator as well as physical device gives network request failed. While I can access same url within browser of emulator.

I have already went through various links, and many people have posted same problem but none of them had ample solution that works. While some people were not able to access localhost via api-call but it was resolved using IP address of system. But in my scenario I am trying to access remote host. Also domain name cannot be used in my scenario, so need a solution using (ip) in fetch method=get.

testlogin = https://10.209.7.115:8080/api/v1/
Basicauth = 'Basic cm9vdDpyb290'

fetch(testingLogin, {
method: "GET",
cache: "no-cache",
mode: "cors",
withCredentials: true,
credentials: "include",
headers: {
'Authorization':Basicauth,
Accept: "application/json",
"Content-Type": "application/json"
}
}).then(response =>
{
if(response.status === 200)
{
this.props.navigation.navigate('Home');
}
else
{
alert("Authorization failed");
}
})
.catch(error => {
alert("Request Failed :Check the ip address Entered:Problem with server ");
throw(error);
})

info
React Native Environment Info:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 54.73 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.4.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 25, 27, 28, 29
Build Tools: 28.0.3, 29.0.0
System Images: android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.3 => 0.59.3
npmGlobalPackages:
react-native-background-fetch: 2.6.0
react-native-cli: 2.0.1
react-native-gesture-handler: 1.3.0

mohsenomidi · 2019-06-22T04:50:23Z

is the issue solved for https??

Trying to fetch data from remote server via api.
Using fetch(https:url:port) to fetch the data. But every time android emulator as well as physical device gives network request failed. While I can access same url within browser of emulator.

I have already went through various links, and many people have posted same problem but none of them had ample solution that works. While some people were not able to access localhost via api-call but it was resolved using IP address of system. But in my scenario I am trying to access remote host. Also domain name cannot be used in my scenario, so need a solution using (ip) in fetch method=get.

testlogin = https://10.209.7.115:8080/api/v1/
Basicauth = 'Basic cm9vdDpyb290'

fetch(testingLogin, {
method: "GET",
cache: "no-cache",
mode: "cors",
withCredentials: true,
credentials: "include",
headers: {
'Authorization':Basicauth,
Accept: "application/json",
"Content-Type": "application/json"
}
}).then(response =>
{
if(response.status === 200)
{
this.props.navigation.navigate('Home');
}
else
{
alert("Authorization failed");
}
})
.catch(error => {
alert("Request Failed :Check the ip address Entered:Problem with server ");
throw(error);
})

TypeError: Network request failed
onerror@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:24051:31
dispatchEvent@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:28695:31
setReadyState@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:28448:33
__didCompleteResponse@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:28275:29
emit@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:3280:42
__callFunction@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:2577:49
http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:2334:31
__guard@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:2531:15
callFunctionReturnFlushedQueue@http://10.0.2.2:8081/index.delta?platform=android&dev=true&minify=false:2333:21

info
React Native Environment Info:
System:
OS: macOS 10.14.5
CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
Memory: 54.73 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.4.0 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
Android SDK:
API Levels: 25, 27, 28, 29
Build Tools: 28.0.3, 29.0.0
System Images: android-27 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5522156
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.3 => 0.59.3
npmGlobalPackages:
react-native-background-fetch: 2.6.0
react-native-cli: 2.0.1
react-native-gesture-handler: 1.3.0

@amohit1315 your issue is not related to this case you are using HTTPS and have an issue, please open another case to report your problem, the workaround solution for http fetch only has been provided in my last comment.

Saumyadip-Pramanik · 2019-06-25T13:25:56Z

React-Native Version: 0.59.0
Axios: 0.18.0
Not working for me! :(

Hi All,

I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml

<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

draperj · 2019-06-25T19:33:47Z

Seeing the same issue using HTTPS connections via Axios and Fetch, running on Android Pie API 28.

Adding android:usesCleartextTraffic="true" to manifests does not resolve this issue.

package.json dependencies:
"dependencies": { "axios": "^0.19.0", "react": "16.8.3", "react-native": "0.59.9" }

Axios and Fetch examples:

axios.get("https://HTTPS_BASED_API_GOES_HERE").then((response) => response.json())
.then((responseJson) => {

    console.log(responseJson);
})
.catch((error) => {
    console.error("Axios error", error);
});
            
fetch("https://HTTPS_BASED_API_GOES_HERE")
.then(response => {

    console.log(response);

    this.setState({
        isLoading: false,
        recentArticles: response.recentArticles,
        tags: response.tags
    }, function () {

    });
})
.catch((error) => {
    console.error("Fetch error", error);
});

amohit1315 · 2019-06-25T19:58:20Z

Hi Everyone,

whoever is facing this problem.
I found a get around. Hopefully someone will fix it in fetch.

Stop using fetch.

Install "'react-native-fetch-blob'"

import it in your js file as

import RNFetchBlob from 'react-native-fetch-blob';

Replace your original fetch as below code

RNFetchBlob.config({
            trusty : true // <---add this
        })
        .fetch('GET', ip1, {
        Authorization : token,
      })
      .then((response) => response.json())
    .then((responseData) => {
        console.log("responseData : " +responseData);
        return responseData
    }).catch((error) => {
        console.log("error : " +error);
        throw(error);
        return {};
    });

trust: true avoids checking for certificates.

Good luck. Comment if you found it useful or not.
All my problems are solved now and working great for both iOS and android.

draperj · 2019-06-25T21:27:35Z

trust: true avoids checking for certificates.

This is unfortunately quite a dangerous workaround that I would not recommend. Your app should always be checking to ensure certificate are valid and not foraged.

mohitmessi007 · 2019-06-25T21:35:57Z

True I agree....

one should always configure certificates.... My scenario was tricky because my app required fetch info from remote host...there could be a thousand or many more and each will have separate certificate

One should use this approach in desperate need only 😊

HIPHOPSANDY · 2020-09-06T15:07:40Z

Add the code then clean Android gradlew then restart your code editor and restart your pc or computer.....

…

On Sun 6 Sep, 2020, 8:35 PM Lanre Adedara, ***@***.***> wrote: @HIPHOPSANDY <https://github.com/HIPHOPSANDY> tried that already, didn't work. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#24627 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJEGMZQGTKJHFPCPIUBPUDSEOQKBANCNFSM4HIW2UQA> .

klever34 · 2020-09-06T15:32:22Z

Same thing @HIPHOPSANDY

HIPHOPSANDY · 2020-09-06T15:38:15Z

Check the image try to implement your code ...

…

On Sun 6 Sep, 2020, 9:02 PM Lanre Adedara, ***@***.***> wrote: Same thing @HIPHOPSANDY <https://github.com/HIPHOPSANDY> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#24627 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJJEGMZTIMSP7R5FQO5XA3TSEOTRRANCNFSM4HIW2UQA> .

klever34 · 2020-09-06T15:43:25Z

I'm not sure I understand that @HIPHOPSANDY

erickhdzreyes · 2020-09-06T16:21:29Z

I'm not sure I understand that @HIPHOPSANDY

Try to adding this permission at the top of the AndroidManifest.xml

HIPHOPSANDY · 2020-09-07T07:29:15Z

are you solved?

blackprinceaj · 2020-09-07T07:39:47Z

yes dear, https instead of httpwork for meSent from my Samsung Galaxy smartphone. -------- Original message --------From: HIPHOPSANDY <notifications@github.com> Date: 07/09/2020 12:29 (GMT+05:00) To: facebook/react-native <react-native@noreply.github.com> Cc: Muhammad Aamir Javed <blackprinceaj@gmail.com>, Comment <comment@noreply.github.com> Subject: Re: [facebook/react-native] Fetch not working on Android 9 API 28 (#24627) are you solved? —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or unsubscribe.

philoskim · 2020-09-17T09:09:51Z

This is my development environment.

$ react-native -v
react-native-cli: 2.0.1
react-native: 0.63.2

$ react-native info
info Fetching system and libraries information...
System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
    Memory: 2.12 GB / 7.64 GB
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 12.18.1 - ~/.local/node/bin/node
    Yarn: 1.22.5 - ~/.local/node/bin/yarn
    npm: 6.14.8 - ~/.local/node/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 14.0.2 - /usr/bin/javac
    Python: 3.7.6 - /home/philos/.local/conda/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found

I solved this problem as follows.

Add this one line to your android/app/src/debug/AndroidManifest.xml file.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools">

    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>

    <!-- An addition starts -->
    <uses-permission android:name="android.permission.INTERNET" />
    <!-- An addition ends-->

    <application android:usesCleartextTraffic="true" tools:targetApi="28" tools:ignore="GoogleAppIndexingWarning" />
</manifest>

Run the following adb commands before you run yarn react-native run-android,
if you use the JavaScript function fetch('http://127.0.0.1:3000/users') in your source code.

# for metro bundler
$ adb reverse tcp:8081 tcp:8081

# for your localhost web server port
$ adb reverse tcp:3000 tcp:3000

$ yarn react-native run-android

That's it! I hope this will help you out.

rutsatz · 2020-12-06T02:55:23Z

This is my development environment.

$ react-native -v
react-native-cli: 2.0.1
react-native: 0.63.2

$ react-native info
info Fetching system and libraries information...
System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
    Memory: 2.12 GB / 7.64 GB
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 12.18.1 - ~/.local/node/bin/node
    Yarn: 1.22.5 - ~/.local/node/bin/yarn
    npm: 6.14.8 - ~/.local/node/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 14.0.2 - /usr/bin/javac
    Python: 3.7.6 - /home/philos/.local/conda/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1 
    react-native: 0.63.2 => 0.63.2 
  npmGlobalPackages:
    *react-native*: Not Found

I solved this problem as follows.

Add this one line to your android/app/src/debug/AndroidManifest.xml file.

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools">

    <uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>

    <!-- An addition starts -->
    <uses-permission android:name="android.permission.INTERNET" />
    <!-- An addition ends-->

    <application android:usesCleartextTraffic="true" tools:targetApi="28" tools:ignore="GoogleAppIndexingWarning" />
</manifest>

Run the following adb commands before you run yarn react-native run-android,
if you use the JavaScript function fetch('http://127.0.0.1:3000/users') in your source code.

# for metro bundler
$ adb reverse tcp:8081 tcp:8081

# for your localhost web server port
$ adb reverse tcp:3000 tcp:3000

$ yarn react-native run-android

That's it! I hope this will help you out.

Thanks. It worked for me. It was missing to disable the warning.

gvsakhil · 2021-02-03T03:27:25Z

Making the backend from http to https works fine

But even after making to https I got an issue and at last I found that SSL was not configured properly

https://www.digicert.com/help/ - U can check ssl configuration is done prorperly or not using this link

SSL NOT Configured properly

SSL Configured properly

hoaxvo16 · 2022-02-24T04:59:45Z

Hi guys, after speding many hour to research about this issue i have this solution: Using ngrok to remote to your local development. So you need:

Install ngrok if you are using ubuntu or debian run the following command:

sudo apt install ngrok
Login and authen token to ngrok
Start BE server
Run the flowing command:

ngrok http <your_back_end_port> --host-header="<your_back_end_port>"

Copy the https url generate by ngrok as an URL to api call for your app. Ex: https://1af4-123-22-24-194.ngrok.io/authentication
Iam using Flipper to debugging by the way, recommend you using this tool , it's very awsome
My BE is ASP.NET incase you need more infomation

donni106 · 2022-03-23T16:35:23Z

https://www.digicert.com/help/ - U can check ssl configuration is done prorperly or not using this link

@gvsakhil thanks, that page helped me to identify some problems, which i hope are the reasons for the fetch not working in our application.

no i am figuring out with some colleagues, how to solve the insecure ones. any helpful suggestions?

donni106 · 2022-03-28T12:06:26Z

i figured out my problem. at the end it was no problem with server and SSL.
i requested data with FormData and 'Content-Type': 'application/json' instead of 'Content-Type': 'multipart/form-data'. would be nice if android would had given some other hints on this beside "Network request failed", as iOS worked well.

flyskywhy · 2022-06-20T00:30:16Z

fixed TypeError: Network request failed when upload file to http not https with Android debug builds

Aiosa · 2022-08-13T09:01:47Z

https://www.digicert.com/help/

Let's encrypt users

Yes, please use this. Even better is https://www.ssllabs.com/ to inspect multiple android devices support at once. Older versions of android might not find a trusted authority in your certificate, especially if you use Let's encrypt. Internet Security Research Group is not enough. Older devices use only TLS 1.2 not 1.3 and the certificate might not be verified.

king-faraz · 2022-11-25T06:30:46Z

instead of trying local host use your android amulator ip address
10.0.0.8

https://10.0.0.8:8081/getcall

github-actions · 2023-05-25T05:00:43Z

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions · 2023-06-01T05:00:54Z

This issue was closed because it has been stalled for 7 days with no activity.

JamesPJ · 2023-07-08T13:17:14Z

I still can't get the API calls working on Android 9. On all other versions of Android works well. And I use cloudflare SSL certificate on my domain. So, not sure what is going on with Android 9. Any help would be appreciated.

leopard1982 · 2023-08-08T06:02:08Z

Hi All,
I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml
<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

That worked for me too. Thanks! @mohsenomidi

I was having the same problem OP had, but using axios and having just updated my cordova android platform to the newest one.

Hai Broooo you save my day!

GeorgeFlorian · 2023-09-25T13:11:12Z

This worked for me on EXPO SDK 49:
I've installed expo-build-properties using npx expo install expo-build-properties and then added it as a plugin in app.json:

    "plugins": [
      [
        "expo-build-properties",
        {
          "android": {
            "usesCleartextTraffic": true
          }
        }
      ]
    ]

PhuNguyen8902 · 2024-05-04T12:00:24Z

Hi All,
I found a work around solution for Http (non HTTPS) fetch :
Add the codes in your main AndroidManifest.xml
<manifest xmlns:tools="http://schemas.android.com/tools"> .... <application android:usesCleartextTraffic="true" tools:targetApi="28"> ... </application> </manifest>

That worked for me too. Thanks! @mohsenomidi
I was having the same problem OP had, but using axios and having just updated my cordova android platform to the newest one.

Hai Broooo you save my day!
Me too thanks you

ZubairAmin695 · 2024-12-20T08:42:03Z

not work for me

mttrthomazelli added the Type: Bug Report label Apr 26, 2019

react-native-bot added Platform: Android Android applications. 🌐Networking Related to a networking API. labels Apr 26, 2019

react-native-bot added the Bug label May 3, 2019

hramos removed the Type: Bug Report label May 6, 2019

jpodpro mentioned this issue Jun 23, 2019

Can't download file with http domain url in android 9 pie joltup/rn-fetch-blob#351

Closed

ahsanu123 mentioned this issue Aug 14, 2021

react native fetch function not working after build and run on real android 11 devices and above #31993

Closed

mattiasnixell mentioned this issue Sep 7, 2021

Why, in case of an error in the url, local translations are not loaded? i18next/i18next-http-backend#71

Closed

github-actions bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label May 25, 2023

github-actions bot closed this as completed Jun 1, 2023

Fetch not working on Android 9 API 28 #24627

Fetch not working on Android 9 API 28 #24627

Comments

mttrthomazelli commented Apr 26, 2019 • edited Loading

🐛 Bug Report

andresmtz98 commented Apr 26, 2019

mttrthomazelli commented Apr 26, 2019

andresmtz98 commented Apr 26, 2019 • edited Loading

0xDub commented Apr 29, 2019

andresmtz98 commented Apr 29, 2019

codypearce commented Apr 30, 2019

hey99xx commented May 1, 2019

mrkacan commented May 2, 2019

codypearce commented May 2, 2019

zhigang1992 commented May 7, 2019

mohsenomidi commented May 7, 2019

mohsenomidi commented May 14, 2019

mmihic96 commented Jun 3, 2019

igorserafim commented Jun 7, 2019 • edited Loading

mathosmor commented Jun 12, 2019 • edited Loading

hohien commented Jun 14, 2019

MobileDevStar commented Jun 20, 2019

amohit1315 commented Jun 21, 2019

mohsenomidi commented Jun 22, 2019

Saumyadip-Pramanik commented Jun 25, 2019 • edited Loading

draperj commented Jun 25, 2019 • edited Loading

amohit1315 commented Jun 25, 2019

draperj commented Jun 25, 2019

mohitmessi007 commented Jun 25, 2019

HIPHOPSANDY commented Sep 6, 2020 via email

klever34 commented Sep 6, 2020

HIPHOPSANDY commented Sep 6, 2020 via email

klever34 commented Sep 6, 2020

erickhdzreyes commented Sep 6, 2020

HIPHOPSANDY commented Sep 7, 2020

blackprinceaj commented Sep 7, 2020 via email

philoskim commented Sep 17, 2020

rutsatz commented Dec 6, 2020 • edited Loading

gvsakhil commented Feb 3, 2021 • edited Loading

hoaxvo16 commented Feb 24, 2022

donni106 commented Mar 23, 2022 • edited Loading

donni106 commented Mar 28, 2022

flyskywhy commented Jun 20, 2022

Aiosa commented Aug 13, 2022 • edited Loading

king-faraz commented Nov 25, 2022

github-actions bot commented May 25, 2023

github-actions bot commented Jun 1, 2023

JamesPJ commented Jul 8, 2023

leopard1982 commented Aug 8, 2023

GeorgeFlorian commented Sep 25, 2023

PhuNguyen8902 commented May 4, 2024

ZubairAmin695 commented Dec 20, 2024

mttrthomazelli commented Apr 26, 2019 •

edited

Loading

andresmtz98 commented Apr 26, 2019 •

edited

Loading

igorserafim commented Jun 7, 2019 •

edited

Loading

mathosmor commented Jun 12, 2019 •

edited

Loading

Saumyadip-Pramanik commented Jun 25, 2019 •

edited

Loading

draperj commented Jun 25, 2019 •

edited

Loading

rutsatz commented Dec 6, 2020 •

edited

Loading

gvsakhil commented Feb 3, 2021 •

edited

Loading

donni106 commented Mar 23, 2022 •

edited

Loading

Aiosa commented Aug 13, 2022 •

edited

Loading