The only way to really protect your PDF documents is by not sending them to the user. How can I avoid the PDF from being downloaded? Some viewers may enforce the “Print” permission saved within the PDF document and disable the “Print” option if the print permissions is off. Different browsers use different viewers, and to our knowledge none of them have a feature to disable downloading. Is it possible to do so by using PDF encryption and permissions?Ī: There is no way to disable the download button on the PDF viewer that displays the document. I do not want users to be able to print or download my PDF files. I was facing the same issue even though I was saving my files to downloads directory.Q: I want disable the “Download” and “Print” options in the browser when streaming PDF files. setDestinationInExternalPublicDir(Environment.DIRECTORY_DOWNLOADS, subPath.getPath()) Here PDF_TYPE is correct and uri is also correct.ĭownloadManager code is also correct here a small snippet. Intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION)
tFlags(Intent.FLAG_ACTIVITY_NEW_TASK | Intent.FLAG_ACTIVITY_NO_HISTORY) It will allow to read/write through READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permission.įor both the file, I am using the same Intent.Īnyone has idea how to change the owner of my downloaded file so that i can gain open or what is the exact reason i am not able to open that downloaded file? Intent intent = new Intent(Intent.ACTION_VIEW) I am also creating a pdf file in Document/myfolder directory, and it can be easily openable using intent and there my app is the owner of that file.Īlso, if I am saving the downloaded file to Document/myfolder directory, it still can't be opened using that intent.Īs per my understanding, from Android 11, they introduced scope storage, and if the owner of that file is accessing it. The same file can be opened from file Manager, though.Īlso, I checked the owner of that file, it is showing and not my app. But in Android 11, I am not able to open the file downloaded from Download Manager. I wasn't facing this issue in Android 9 and in Android 10 i opted out for Legacy Storage.
0 kommentar(er)
