Skip to main content

Hello everyone!

We encountered a problem with the PDF viewer on Android's Chrome browser. It does not display the PDF-viewer, and we tested this on a more recent version of Android, and an older version of Android:

Now this is what we get when we open it on Chrome. When we open it on a browser like FireFox, or Microsoft Edge, we get exactly the PDF we ask for. It shows the PDF viewer, on the newer Android and older Android versions. 


In the following release notes this should have been fixed: 

We have our web server settings set correctly as far as I know. So why would it still fail to show on Chrome? It does work on Firefox and Microsoft Edge. This is already good news, but we cannot predict what kind of browsers our end users will use.

Hi @SanderAdam,

I just verified on the latest version (2024.3.11.0) that the PDF preview does work for me on Android Chrome.


Can you please create a TCP ticket so we can research what is happening in your specific case?

Thanks in advance!

Kind regards,
Leroy Witteveen

Hi Leroy,

I will first check our server again, as it does work on our development environment. Our test environment might have a slight difference. If there is no difference in configuration, I will make a ticket.

Thanks for your reply!

Kind regards,
Sander Adam

Hi ​@Leroy Witteveen,

I am sorry for the delayed reaction, but I have checked the web.config on our web servers and I saw that the MIME-types are already in the web.config.

Could there be a difference between the way Azure and IIS interpret these mime types, because on the configuration of our Software Factory, which runs on IIS, everything works. But when I try to do it on our environments that run on an Azure configuration, then I get the grey screen, but solely on Google Chrome for Android.

Kind regards,
Sander Adam

Hi ​@SanderAdam,

I think the best route to go for this is to create a TCP ticket, then we can investigate in detail and also reproduce it on your specific environment.

Thanks in advance!

Kind regards,
Leroy Witteveen

Reply


Terms & ConditionsCookie settings