Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I can connect to my web api in debug mode but when I build a release apk the Android app will not connect to the site at all. Does Android recognize Let’s Encrypt Certs? If so, how can I confirm?
That is a great point and I did check that by having the app display a message with the address prior to posting. There is only one BASE URL which is https://wr.significantdigits.com. In debug it works perfectly.
I am certain because I call this exact same code from debug and works perfectly. I have also forced the app to pop up the url for display so I could confirm the address and it was correct.
By they way, I do sincerely appreciate all of the assistance I am getting with my question.
Let me restate this, in debug I receive the full json return object. In release the response is null. In my web api I modified it to log as soon as anything hit the authentication controller. Nothing gets logged.
I have confirmed that my code was masking an error. It is still not fixed but I have confirmed the error is not the certificate. Thank you everyone for your guidance.
To add more detail and for others that may have this issue, the problem turned out to be a release build setting. In Android Studio - > Build - > Build Types under the release build type there is a setting called minify. If it is set to true Android Studio will decide what to “optimize”. It sometimes drops items incorrectly that it thinks is not needed. When I set this to false, my authentication object would then pass to my web api.