What do these errors indicate?
These errors state that the request you tried to make did not reach your remote server. Be it a hosted API or your local machine. These errors may occur under the following scenarios:
Scenario 1
If we want to serve the mobile app with your local machine’s REST endpoint which has the local server up and running. We must choose “public IP” of the local machine to be the endpoint.
Scenario 2
You can access APIs over HTTP pointing to a domain name or an IP. However, these approaches are not suggested as you wouldn’t want your APIs to be unsecured or the server’s IP to be used as an endpoint.
Scenario 3
If you access the API over HTTPS with a domain name and receive a “Network Error”. Try checking the access logs and error logs of the servers to check if the API messed up with the “request” or did the request never reach the server. If the request did not reach the server, this indicates the REST endpoint is rejected to be served by the Android itself.
Solution
To resolve this issue check if your SSL certificates on the servers are correctly installed. Go to: https://www.ssllabs.com/ssltest/ to find more about your SSL certificate.
If you get the warning “certificate chain is incomplete” and the overall rating is below “A+”. Try resolving the issue by installing the complete certificate chain on the respective server and check for the ratings again.
If things are done right the ratings should be increased to A+
Now your mobile application should be able to access the API over HTTPS with a domain main.
Facing any other issues related to Android applications? We would like to hear about them. Drop us a word at business@qed42.comWhile accessing an API within the Android application you might be haunted with the ‘Network Error`: