Copy link to clipboard
Copied
Hi Team,
We have one pdf file that is downloading from server through our mobile app. When we open this pdf file in Adobe Acrobat for mobile on any Android devices, files does not display whole content. While same pdf file when we open through Adobe Acrobat Reader DC on Desktop then all content display successfully.
This pdf file display whole content on Android devices, when we open it through other non-adobe products like WPS office, Drive Pdf viewer etc.
We debug from our side and we are not getting any error.
Kindly check it and let us know as soon as possible. Please let us know in case of any query.
For reference attaching the pdf file, and also attaching the screenshot of pdf that how this pdf is looking into mobile devices, how this pdf is looking into desktop devices for Adobe Acrobat.
As I see there is not any option to attach the pdf files, please let me know how I can send pdf files for inquiry. Is there any email id of support team in Adobe Acorbat then please let us know.
Mobile Snanpshot of Pdf -
Desktop Snanpshot of Pdf -
Thanks
Qfix Team
Copy link to clipboard
Copied
OK. The Director of our Mobile PDF Reader development team found the problem. In fact the PDF file is defective although some renderers ignore the error.
There is a DecodeParams array that is empty. We fixed the file by removing that array. See attached file. It should work. Bottom line is that whatever is creating this file (it is not Adobe) is not following the PDF specification closely enough.
- Dov
Copy link to clipboard
Copied
Same issue here. Also noticed that hapens with Adobe app on UWP windows devices.
Copy link to clipboard
Copied
You are posting replies to a PUBLIC FORUM. Do not upload files containing personal data.
Copy link to clipboard
Copied
Thanks Dave. Dont worry about that. This file does not provide classified information. It's just my weight and can be public used to help solving this problem.
Copy link to clipboard
Copied
You can't upload files here. If you want/need to post anything other than screen shots, you need to put them on a file sharing service and give us a pointer to same.
If you have Acrobat DC, you already have access to such a service in Acrobat desktop as Send and Track.
- Dov
Copy link to clipboard
Copied
Thank you, Dov. I did it. But the message with the link was deleted. Probably because there is personal (non relevant) information. I really appreciate your help.
Best regards.
Copy link to clipboard
Copied
Send me a private message on the forums with the link and I'll the file that way! Sorry for the inconvenience. We really want to assist you.
- Dov
Copy link to clipboard
Copied
OK. We've got your file. I've run the obvious preflight checks in Acrobat Pro DC Preflight.
There are some font issues associated with the font definitions' CIDToGIDMap, but those problems are not such that they should block all screen display:
Quite frankly, I haven't seen an issue like this one before, but there definitely is a problem.
Since the file does display with our desktop products but not our mobile viewer on either iOS or Android, I will forward the file to our mobile development team for their analysis.
- Dov
Copy link to clipboard
Copied
Just for information. I tried to visualize this file on a W10M device too (Lumia 950). Tried with Edge and could not open the file either. I don't know if this information can provide some help.
Many thanks Dov.
Copy link to clipboard
Copied
That is helpful information. Thanks. May take a bit to get back to you on this. As you are probably aware, this PDF file wasn't generated by any Adobe tools and thus, it may take some significant work to figure out what's wrong.
- Dov
Copy link to clipboard
Copied
Thanks Dov for passing the file on to me. I had a brief look at it. The Mobile Acrobat products seem to be throwing an exception in getting the DecodeParams entry from the Contents stream on each page. Looking in some of our internal tools, I can see that the Contents stream has an empty DecodeParams array. The PDF Specification (as I read it, though I'm not an expert) seems to say that the DecodeParams entry is optional if the Filter uses default parameters, but it does say that if the entry is present (and it is), it shall have an entry for each filter (in this case, a FlateDecode filter), which this PDF does not. It looks like the desktop Acrobat is treating the empty entry as if the entry weren't present at all. I verified that by removing the DecodeParams array from the Contents streams (on each page), the PDF renders on the mobile clients. Please contact Dov or me if you'd like a copy of the "fixed" PDF (I'm not sharing it on the forum in case it's something you'd rather not have shared). I'm going to file a bug in the mobile product to be more forgiving of this generation error, but I can't promise when it will be fixed.
Copy link to clipboard
Copied
OK. The Director of our Mobile PDF Reader development team found the problem. In fact the PDF file is defective although some renderers ignore the error.
There is a DecodeParams array that is empty. We fixed the file by removing that array. See attached file. It should work. Bottom line is that whatever is creating this file (it is not Adobe) is not following the PDF specification closely enough.
- Dov
Copy link to clipboard
Copied
If you could please post a sample PDF file exhibiting this issue, we might be able to examine it and advise you as to what the issue actually is. Without such a file, there is nothing we can do other than provide perhaps meaningless speculation.
- Dov
Copy link to clipboard
Copied
No it isn't. It is screen shots, not the PDF file itself!! We can't analyze screen shots to determine the contents of a PDF file.
- Dov
Copy link to clipboard
Copied
Hi Dov, Can you please let me know how I can send pdf files to you
Copy link to clipboard
Copied
Use the Send and Track feature of Acrobat and send me the URL via a private message on these forums.
- Dov
Copy link to clipboard
Copied
Hi Dov, Please find the pdf file in below link : https://files.acrobat.com/a/preview/74fc799b-36b6-4bd7-896e-29dfc6b92ccd
Copy link to clipboard
Copied
Thanks. Got the file.
Observations:
(1) Yes, when opening the file in the iOS version of the Adobe Reader Mobile application, I indeed get the same results as you see in the Android version. Something is very wrong.
(2) It opens and displays with no problem in Adobe Acrobat Pro DC on Windows.
(3) I then used the Save as Other => Optimized PDF… function in Adobe Acrobat Pro DC on Windows to save an “optimized” version of the file using the following parameters:
(4) I opened the resultant file (see attached PDF file) and it properly displayed the whole page without a problem. I'll send your original sample off to our mobile engineering team for their analysis of why the original file had “issues.” Generally, these problems occur due to some minor infraction of the PDF standard. The code for our mobile version is significantly different than our desktop software that there may be differences in terms of the tolerance of errors in an incoming PDF file. (For the record, the PDF file was not originally generated by any Adobe software components!)
- Dov
Copy link to clipboard
Copied
Hi Dov, What needs to be change? Is there any changes required from our side in pdf form. Since the pdf in coming from server side, so in the we can't do anything in code for mobile side. Please let us know is there any changes required from server side. Or Adobe team will do needful to display the content in file. Please clarify in detail.
Copy link to clipboard
Copied
I passed your file to our mobile engineering group which will evaluate what exactly is wrong with the file and whether there is anything we could or should do to allow whatever idiosyncrasy in that particular file causes it not to fully and properly display on mobile, but properly display on the desktop.
- Dov
Copy link to clipboard
Copied
Even I have the same problem please help me with this pdf it is very important for me thank you
Copy link to clipboard
Copied
Thank you for sharing the file.
Our team is aware of the issue, and will be fixed in the upcoming update.
While I understand how frustrating this might be, I request your kind understanding and patience while we get this fixed.
-Souvik
Copy link to clipboard
Copied
to work

