HTTP/S does not work in Android release build

shiziluosidao · June 17, 2016, 7:53pm

Hey guys,

I built an app using the $http service which works nice in debug mode.
However, when I build a release and run it on Android none of the requests work (neither HTTP nor HTTPS).
What I did so far:

whitelist plugin reinstalled
put into config.xml: <access origin="*" subdomains="true" /><allow-navigation href="https://*/*" /><allow-navigation href="data:*" />
added to index.html: <meta http-equiv="Content-Security-Policy" content="default-src 'self' https: ; style-src 'self' 'unsafe-inline'; script-src 'self' https: 'unsafe-inline' 'unsafe-eval' ">
Added ng-csp to <body> tag
made sure the HTTPS works fine (via ssllabs.com)

What could I have missed? Spent lots of time reading and trying, but no success to this point :-/

Shi

frcol · June 17, 2016, 8:52pm

Did you try to run it in device like “ionic run android”?

shiziluosidao · June 17, 2016, 9:01pm

Sure, as I wrote debug mode works. Only after “ionic build --release android” all http/s requests fail.

pliablepixels · June 17, 2016, 11:59pm

are you using self signed certificates? If so, you either need to make changes to SystemWebViewClient.java or use some plugins. I had a custom version of SystemWebViewClient to enable SSL to work with untrusted certs, but crosswalk uses other files, so I landed up just switching between two different plugins based on which build I was creating (with or without xwalk)

github.com

pliablepixels/zmNinja/blob/master/build_android.sh

#!/bin/bash

# App signining credentials in this file
NINJAKEYSTORE=~/Desktop/zmNinja.keystore

if [ ! -f "$NINJAKEYSTORE" ]; then
        echo "zmNinja keystore not found"
        exit
fi

mkdir release_files
rm -f release_files/*

# no arguments - build both
# 1 == build crosswalk only
# 2 == build native only
BUILD_MODE="all"
if [ "$1" = "1" ]; then
        BUILD_MODE="xwalk"
        echo "only building crosswalk"

This file has been truncated. show original

shiziluosidao · June 18, 2016, 5:15pm

Thank you. The certificate is by Let’s Encrypt and ssllabs or Chrome browser did not find any problems.
What I find most strange is, that even HTTP (without S) does not work, the .error(function(data) { … }) gives me undefined for data :-/
I tried the crosswalk plugin without success, only the HTTPS requests seem to take much longer until I get to see the error message.

Any more ideas?
Is there a way to debug this in a release build?

delpiero22 · June 19, 2016, 6:11am

same my app. I test on browser so cool faster and post service work done.but when i build on device perfomance so slow and my button for post json not work.I tried alert pop up in method http.post for show any event handling but not anything. another solution I reinstall cordova whitelist,edit config.xml–> ,edit index.html same you and add getbutton(http.get)and alert for check.so it works but post button not work.

cordova :6.2
node :6.2
Ionic Version: 2.0.0-beta 8

pliablepixels · June 19, 2016, 12:53pm

If neither HTTP nor HTTPS are working, the chances are very high its a Content Security Policy issue.
Can you try using this one, verbatim and see what happens?

github.com

pliablepixels/zmNinja/blob/master/www/index.html#L9


<!DOCTYPE html>
<html>


<head>
<meta charset="utf-8">




<meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover">      


<meta http-equiv="Content-Security-Policy" content="img-src * blob: android-webview-video-poster: cdvphotolibrary:  'self' data: ws: wss://*; default-src * blob: 'self' gap: wss: ws: data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src * http: https: ws: wss:;">




   


<!--<meta http-equiv="Content-Security-Policy" content="img-src * blob: android-webview-video-poster: cdvphotolibrary:  'self' data:; default-src * blob: 'self' gap: wss: ws: ; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval';connect-src * http: https: ws: wss:;">-->
<title></title>
<meta name="format-detection" content="telephone=no">
<link rel="stylesheet" href="css/animate.min.css">
<link rel="stylesheet" href="css/angular-circular-navigation.css">

And then try a simple $http.get

shiziluosidao · June 20, 2016, 6:08pm

Thank you, now it works with HTTP and https://www.google.de. So I’m guessing it is a self-signed cert issue. But the certificate got rated A+ by ssllabs.com Is it possible that the Ionic library does not accept Let’s Encrypt yet?

shiziluosidao · June 21, 2016, 12:26pm

Ok, resolved / dammit
Locally the domain is resolved to a local IP address going a different route with a different certificate. @Pliablepixels, thanks for your great support!

pliablepixels · June 21, 2016, 4:46pm

Ah, good catch. Glad you solve it!

elduderino15 · June 1, 2017, 6:24am

Hi @shiziluosidao , could you please have a look at my problem. It seems to be similar to yours…

prateek610 · September 27, 2017, 9:38am

@shiziluosidao Can you please tell me how did you resolve the issue. I have also tried everything suggested everywhere but not solution.
Banging my head from past 2 days.

shiziluosidao · October 4, 2017, 2:12pm

My problem was an Apache server with an incorrectly configured HTTPS certificate. Therefore it did not load the page. If your server is properly setup (with like LetsEncrypt) it should work when allowing access in your config.xml

prateek610 · October 5, 2017, 3:59am

@shiziluosidao

Can you please elaborate what was incorrect in your HTTPS setup. When I check my url on ssl checkers they respond “it is correct”.
By “Allowing access in config.xml” you mean this…???

fdambrosio · October 26, 2017, 5:13pm

I have the same problem, how did you solve it?

kaustubhj1 · February 5, 2018, 11:32am

Hey shiziluosidao

Can you describe the steps you have taken to resolve this issue. I am facing similar issue while getting build from creator side of ionic.

Thanks

fdambrosio · March 26, 2018, 12:34pm

how did you verify that this is an invalid certificate? I have the same problem but the site certificate works correctly on browsers and the ssl check tells me that the certificate is valid. But I have seen that the problem occurs only on android devices <5.1

shiziluosidao · March 29, 2018, 8:49pm

I had a local DNS pointing differently at the website (without reverse proxy), so it accessed a different webserver (not the reverse proxy).

Topic		Replies	Views
HTTPS status 0 in the release build ionic-v1	2	2113	February 23, 2016
Ionic release android	7	1413	February 6, 2015
$http requests on a built app ionic-v1	2	1118	August 12, 2015
Release build kills http request ionic-v3	2	1836	October 26, 2017
Android release can't connect to https ionic-v3	2	1188	June 10, 2016

HTTP/S does not work in Android release build

Related topics