org.apache.http.legacy doesn't work on API 28
To begin with, I was using org.apache.http functions for a while now and error came when I tried to launch my app on API 28. It's working on API 26 and API 23, but suddenly something is wrong with API 28. Did Google made some changes?
android apache http asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
add a comment |
To begin with, I was using org.apache.http functions for a while now and error came when I tried to launch my app on API 28. It's working on API 26 and API 23, but suddenly something is wrong with API 28. Did Google made some changes?
android apache http asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26
add a comment |
To begin with, I was using org.apache.http functions for a while now and error came when I tried to launch my app on API 28. It's working on API 26 and API 23, but suddenly something is wrong with API 28. Did Google made some changes?
android apache http asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
To begin with, I was using org.apache.http functions for a while now and error came when I tried to launch my app on API 28. It's working on API 26 and API 23, but suddenly something is wrong with API 28. Did Google made some changes?
android apache http android apache http asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
asked Nov 26 '18 at 13:35
John EvansJohn Evans
1
1
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26
add a comment |
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26
add a comment |
2 Answers
2
active
oldest
votes
Apache HTTP client deprecation
With Android 6.0, we removed support for the Apache HTTP client.
Beginning with Android 9, that library is removed from the
bootclasspath and is not available to apps by default.
answered Nov 26 '18 at 13:40
ossoss
33117
add a comment |
Step 1:
create an xml file in res/xml/network_security_config.xml and copy the below code in it,
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">your.website.domain</domain> <!-- the domain you are using for api network call -->
</domain-config>
</network-security-config>
Step 2:
now in your Manifest.xml add android:networkSecurityConfig="@xml/network_security_config" under the <application> tag. Done!
answered Dec 12 '18 at 9:08
AsadAsad
165417
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482314%2forg-apache-http-legacy-doesnt-work-on-api-28%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Apache HTTP client deprecation
With Android 6.0, we removed support for the Apache HTTP client.
Beginning with Android 9, that library is removed from the
bootclasspath and is not available to apps by default.
answered Nov 26 '18 at 13:40
ossoss
33117
add a comment |
Apache HTTP client deprecation
With Android 6.0, we removed support for the Apache HTTP client.
Beginning with Android 9, that library is removed from the
bootclasspath and is not available to apps by default.
answered Nov 26 '18 at 13:40
ossoss
33117
add a comment |
Apache HTTP client deprecation
With Android 6.0, we removed support for the Apache HTTP client.
Beginning with Android 9, that library is removed from the
bootclasspath and is not available to apps by default.
answered Nov 26 '18 at 13:40
ossoss
33117
Apache HTTP client deprecation
With Android 6.0, we removed support for the Apache HTTP client.
Beginning with Android 9, that library is removed from the
bootclasspath and is not available to apps by default.
answered Nov 26 '18 at 13:40
ossoss
33117
answered Nov 26 '18 at 13:40
ossoss
33117
answered Nov 26 '18 at 13:40
ossoss
33117
answered Nov 26 '18 at 13:40
ossoss
33117
33117
add a comment |
add a comment |
Step 1:
create an xml file in res/xml/network_security_config.xml and copy the below code in it,
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">your.website.domain</domain> <!-- the domain you are using for api network call -->
</domain-config>
</network-security-config>
Step 2:
now in your Manifest.xml add android:networkSecurityConfig="@xml/network_security_config" under the <application> tag. Done!
answered Dec 12 '18 at 9:08
AsadAsad
165417
add a comment |
Step 1:
create an xml file in res/xml/network_security_config.xml and copy the below code in it,
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">your.website.domain</domain> <!-- the domain you are using for api network call -->
</domain-config>
</network-security-config>
Step 2:
now in your Manifest.xml add android:networkSecurityConfig="@xml/network_security_config" under the <application> tag. Done!
answered Dec 12 '18 at 9:08
AsadAsad
165417
add a comment |
Step 1:
create an xml file in res/xml/network_security_config.xml and copy the below code in it,
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">your.website.domain</domain> <!-- the domain you are using for api network call -->
</domain-config>
</network-security-config>
Step 2:
now in your Manifest.xml add android:networkSecurityConfig="@xml/network_security_config" under the <application> tag. Done!
answered Dec 12 '18 at 9:08
AsadAsad
165417
Step 1:
create an xml file in res/xml/network_security_config.xml and copy the below code in it,
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">your.website.domain</domain> <!-- the domain you are using for api network call -->
</domain-config>
</network-security-config>
Step 2:
now in your Manifest.xml add android:networkSecurityConfig="@xml/network_security_config" under the <application> tag. Done!
answered Dec 12 '18 at 9:08
AsadAsad
165417
answered Dec 12 '18 at 9:08
AsadAsad
165417
answered Dec 12 '18 at 9:08
AsadAsad
165417
answered Dec 12 '18 at 9:08
AsadAsad
165417
165417
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53482314%2forg-apache-http-legacy-doesnt-work-on-api-28%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"Something is wrong" is not a really good description of the error you are facing
– Nico Haase
Nov 26 '18 at 14:26