PDF Opening Issues

Fix Cannot Open a PDF in Adobe Acrobat from Another Android App

Elise Williams Oct 19, 2026 868 views

Question details

Users and developers encounter an access error when attempting to launch a PDF file in Adobe Acrobat via an intent from a separate Android application.

Fix Cannot Open a PDF in Adobe Acrobat from Another Android App

Product: Adobe Acrobat for Android
Device & OS: Android N (API level 24) or later
Scenario: Attempting to open and view a local PDF document triggered by a third-party application's share or open-in functionality.
Observed behavior: Adobe Acrobat fails to load the document and displays the error message: 'This file could not be accessed. Check the location or the network and try again.'

Before you start

Verify that the PDF file actually exists at the specified storage path and is not corrupted by trying to open it natively through the Android file manager.

Solution 1Recommended

Configure FileProvider and Grant Read Permissions

Implement a secure content URI and assign the necessary read permissions to allow external PDF readers to access the file securely.

Starting with Android N, the operating system enforces StrictMode, which prohibits sharing standard 'file://' URIs between applications. To resolve the 'file could not be accessed' error, developers must wrap the file path using Android's FileProvider system and explicitly grant temporary read access to the receiving application.

Define File Paths in XML

Navigate to your project's 'res/xml' directory. Open or create 'filepaths.xml' and ensure it correctly declares the specific directory (such as external-cache-path or files-path) where your PDF is stored.

Generate a Content URI

In your Java or Kotlin activity, replace 'Uri.fromFile(file)' with 'FileProvider.getUriForFile(context, authority, file)' to generate a secure 'content://' URI for the PDF.

Assign Read Permission Flags

Before launching the intent, add the explicit read permission by calling 'intent.addFlags(Intent.FLAG_GRANT_READ_URI_PERMISSION);'. This authorizes Adobe Acrobat to read the temporary content URI.

Launch the PDF Viewer

Execute 'startActivity(intent)' to trigger the document viewer. Adobe Acrobat should now bypass the access restriction and successfully render the PDF.

Targeting Android 11+ Storage Changes: If your app targets Android 11 (API level 30) or higher, also ensure you have the appropriate package visibility queries declared in your AndroidManifest.xml so your app can detect installed PDF viewers.

Open PDFs Seamlessly on Android

Use WPS Office as Your Default Android PDF Reader

Bypass third-party app access errors and view your documents instantly. WPS Office for Android provides robust handling of system intents and local files, ensuring you can read, annotate, and manage PDFs effortlessly without running into FileProvider access restrictions.

1. Download WPS Office: Open the Google Play Store on your Android device, search for 'WPS Office', and tap 'Install'.
2. Locate Your Document: Navigate to the PDF file using your device's native File Manager or the third-party application you are trying to share from.
3. Select WPS Office: Tap on the PDF file. When the 'Open with' system dialog appears, select the 'WPS Office' icon from the list of available apps.
4. Set as Default Application: To prevent future intent errors and streamline your workflow, tap 'Always' to establish WPS Office as your permanent default PDF viewer.

Seamless integration with Android intent mechanisms to prevent file access errorsFully compatible with Microsoft Office formats (Word, Excel, PowerPoint) and native PDFsLightweight application footprint that preserves your device's memory and batteryFree built-in tools for annotating, highlighting, and signing PDF documents

microsoft office alternative - wps office

Frequently Asked Questions

Why do I get a 'file could not be accessed' error when opening PDFs on Android N?

Starting with Android N (API level 24), the OS blocks the direct sharing of 'file://' URIs between apps for security reasons. Apps must now use 'content://' URIs paired with temporary read permissions via FileProvider to share files securely without triggering access errors.

Does this FileProvider restriction affect all PDF readers on Android?

Yes, any PDF reader or external application running on recent Android versions requires a properly configured content URI and explicit read permissions to access files located in another application's private storage directory.

Can I fix this PDF error if I am just a user and not the app developer?

If you are an end user, you cannot modify the application's internal code to fix the intent configuration. As a reliable workaround, manually save or export the PDF to your device's public 'Downloads' folder, then open it directly from a file manager using your preferred PDF reader.

PDF Troubleshooting