TOPIC:

Hello,
We are using Radaee Android SDK for a long time now, without a single issue. But now, we are getting a completely white render instead of the properly rendered document.
The only difference from before is the document itself. The pdf document now contains extra info fields. We can see these fields were properly introduced, and the document is valid in other pdf renders.
We assume this is some kind of bug, because there is not any error besides the visual one! Radaee can even read the document fine. It reads the number of pages fine as well. Only the rendering seems wrong, as it is a complete white page.

Attachment 1 is the info fields seen in adobe acrobat.
Attachment 2 is the screenshot from the sample application to demonstrate the problem.

Any tips?

Cheers

It seems a bug or a corrupted file.
May you provide the PDF file, please?
Which SDK version are you adopting within your application?

Hi,
unfortunately, i can't provide the pdf file. Yet, while trying to build a sample to show you the error, using the same exact methods BUT with a different PDF file, the file was rendered without any issue!
When calling the Global.getVersion() method i get a 201407 ... It seems like it.
I'll investigate a bit further, but for now, it seems that the error is something related to the pdf file. Yet, it is weird that others pdf readers like Adobe PDF can render the file, and radaee can't.
I'll try to reproduce the error with a file i can pass on to you guys.
Thank you

After trying with distinct documents, i noticed that, the ones that didn't got rendered after my operations were PDF versions 1.4 (Acrobat 5.x) and the one that got correctly rendered was a pdf file with PDF version 1.7.
Could this be the issue?

PDF 1.4 is lacking many features (ie.: transparencies for annotations) but RadaeePDF should render them without any issues.
We own a huge library of PDF1.4 - 1.7 files and we use that library to test our library while releasing new versions.

The issue could be on the file itself or in an unpredicted combination of features but, as told, the only way to solve the issue is to directly check your file.
May you provide the creation date of .so files in your libs/jniLibs folder?

Updating the .so files actually solved the issue! Thanks for the tip. Was a little reticent to doing that simply because of the stability of my project, but it seems to work just fine.
Thank you for your time