"exposed beyond app through Intent.getData()"

[pd4321]

Hi,
I wanted to transform this part of the code for opening a PDF file in Windows to Android::

path_to_acrobat = os.path.abspath('c:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe')
process = subprocess.Popen([path_to_acrobat, '/A',str(strana) , path_to_pdf], shell=False, `stdout=subprocess.PIPE)`

I compiled this

    async def openFileDialog(self, widget):
        from toga.platform import current_platform
        if current_platform == "android":
            from android.content import Intent
            from java.io import File

            try:
                file = File(str('/data/data/cz.pd.Level/files/chaquopy/AssetFinder/app/Level/resources/LEVEL 281.pdf'))
                intent = Intent(Intent.ACTION_VIEW)
                FileProvider.getUriForFile(MainActivity.this, BuildConfig.APPLICATION_ID + ".provider",file)
                intent.setFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION)
                result = await self.app._impl.intent_result(intent)

            except Exception as chyba:
                self.main_window.info_dialog(f"Chyba", f"{chyba}")

Instead of opening the file I get the error "exposed beyond app through Intent.getData()". Do you know what to do about it?

They came up with something here. But I don't understand how to use it in Toga/Python

In the future, I want to open it from internal memory/memory card. But now I don't want to deal with access rights issues, so I put the file in resouces.

Thanks

[freakboy3742]

I'm not entirely clear on what it is you're trying to do.

Your original code uses subprocess to start a completely separate process to open a file. That approach won't work on Android, because you can't use subprocesses.

However, File intents aren't really what you want either. A File intent is the analog of Python's open() method - that won't "open" a file in the sense of "loading it into Acrobat", it "opens" a file so it can be read on a byte-by-byte basis.

It sounds like what you want is the Action View Intent - that's the mechanism you'd use to open a URL in a web browser, AFAIK the same approach is used for any URL scheme or content type, and it's up to the device to determine how to satisfy that View request.

However, that approach also won't work with a file in your app's resources, because that won't be a URI that is visible to another application (which is what you need to "open in acrobat" on Android). It also presumes that the user has an app installed that can handle PDF content (i.e., that they have acrobat, or an analog of it, installed).