Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APV won't open locally-stored PDFs #160

Open
GoogleCodeExporter opened this issue Aug 17, 2015 · 2 comments
Open

APV won't open locally-stored PDFs #160

GoogleCodeExporter opened this issue Aug 17, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. When loading a PDF from a web link, it will download and APV (v0.4.0) will 
load it just fine.
2. Trying to open the *same* PDF files from /storage/emulated/0/Downloads using 
File Manager results in APV crashing instantly on opening.
3. APV's own built-in browser shows no files or folders under 
/storage/emulated/0 (even though there are many).

What version of the product are you using? On what operating system?

Running Android 4.4.2 on Nexus 5 (Cyanogenmod 11-M7)
APV v0.4.0 (I also tried downgrading to v0.3.x and had the same issue)

I'm a bit confused about whether this is a problem with APV itself, or some 
kind of permission problem. It's puzzling that APV can open downloaded PDFs 
directly, but can't open them from File Manager and can't browse to them itself.

Original issue reported on code.google.com by dlen...@gmail.com on 27 Jun 2014 at 12:13

@GoogleCodeExporter
Copy link
Author

i can confirm same problems, unable to see any files on the filesystem when 
browsing within APV.  i can browse directories but no files are shown.  if i 
browse using a file manager and try to open the PDF file, APV instantly 
crashes.  also running Android 4.4.2, stock Galaxy S5 firmware.  it seems like 
a strange permission problem; i notice similar problems when i connect my phone 
via USB to my Linux workstation: i can browse the filesystem of /sdcard but no 
files are shown....

Original comment by scarlion...@gmail.com on 14 Apr 2015 at 7:32

@GoogleCodeExporter
Copy link
Author

This is the same as issue 150. Adding READ_EXTERNAL_STORAGE permission fixes it.

Original comment by olaf.die...@gmail.com on 19 Apr 2015 at 1:31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant