Hi TK_ITA,I was able to download the app and get into the RESULTS section from within the in-app browser. However, all of the results were in HTML. They all successfully opened up within the in-app Webview. Can you share with me the exact URL that is linked from within the app? Feel free to send it privately if it is sensitive.Thanks,Kirk

Hi Keith,Thank you for the URLs. You provided both an HTTP URL that redirected to an HTTPS URL, as well as an independent HTTPS URL. The HTTP URL responds with a 301 that redirects to an HTTPS URL. Both HTTPS URLs return 503s (meaning they are unavailable). Can you let me know when your HTTPS web server is working again or send me different URLs? I'm testing via curl:> curl -I [HTTPS_URL]HTTP/1.1 503 Service Unavailable> curl -I [HTTP_URL]HTTP/1.1 301 Moved PermanentlyLocation: [DIFFERENT_HTTPS_...

Hi Keith,Can you verify that you've specifically been able to reproduce the https issue with Acrobat Reader (and not another PDF reader)? It is the burden of the PDF reader to handle the https intent and not all PDF readers handle https intents. Also, can you include the URL of the PDF which you're testing? [Feel free to scramble the domain and/or some of the letters - I'm interested in the overall structure and placement of non-alpha characters.] Thanks,Kirk

Hi Keith,Android does not ship with a default PDF reading experience, so Android users view PDFs through third party apps like Adobe Reader. This is different than iOS, which includes PDF rendering within the browser. At the time of this writing, AEM Mobile does not support the rendering of arbitrary PDFs in the in-app web browser (or anywhere outside of articles), so the customer leaves the app to view a PDF delivered directly from an HTTP endpoint.If there is a PDF renderer app like Adobe Read...