Bug Text problem since last update (Nexsus 5)

[Millgid]

After the recent update of the reader, most of my PDF's have become mostly unreadble. Much of the text has been converted to little black boxes with small crosses in them. I use and recommend the app to most of my clients. Sadly I'll have to find another app if this isn't fixed quite quickly.

Not sure what you've done but you've broken it!

[cherry]

Hi Millgid,

Could you please provide the following info?
1) Version info of your Foxit Reader;
2) An original copy of the PDF document and the one that with black boxes with small crosses;
3) How to replicate the problem;
4) Version info of your Android.

[Millgid]

Hi Millgid,

Could you please provide the following info?
1) Version info of your Foxit Reader;
2) An original copy of the PDF document and the one that with black boxes with small crosses;
3) How to replicate the problem;
4) Version info of your Android.

1. Version 3.1.1.1210 Foxit MobilePDF reader as of the 11th December (And the previous version as of the 1st december)

2. Original pdf (1001.pdf) uploaded along with two screen shots.. one on my phone and one on my desktop.. both using Foxit software and loading the same pdf.

3. I load the pdf on the mobile version.. nothing else.

4. My phone is running Android Lolipop 5.0 (Nexus 5)


As I said in my original post, It was working just fine before the mobile version of foxit got updated on the 1st December. Now I can't use that app at all. infact I've had to install Xodo for the time being. I'd rather be using Foxit.

Ok, The foxit website seems to not like uploading things. a few links below.

PDF FILE : https://www.dropbox.com/s/pqi343tr5x6l7hy/1001.pdf?dl=0

Screenshot of if running on my phone: https://www.dropbox.com/s/a0fylrr5f8...phone.png?dl=0
Screenshot of if running on my Desktop :https://www.dropbox.com/s/ge7rkmimyt...sktop.png?dl=0

[Millgid]

Any update or feedback from my bug report yet?? Seem to be left dangling here!

[richell_huang]

Sorry for the delay. We did not forget it, this issue has been reported to our internal bug tracking system for further investigation. Report ID#: 63248. I've monitored this issue and will keep you posted with the update.

[richell_huang]

Good news, this issue will be fixed in next release.