[Bug] Can't open a downloaded PDF from the new Downloads section

[vesta0]

Steps to reproduce

• Download a PDF file (tried this twice, that's why there are 2 files in the screenshot)
• Open the new Downloads section in the browser and tap to open the file

Expected behavior

• File opens

Actual behavior

• Receive an error message (see screenshot)

Notes

• The file can be successfully opened through Android default file manager. So it was not a case of a failed/corrupt download. When opening from the Android default file manager, the files can be opened successfully using the default file browser, adobe, google drive, and kindle.

Device information

• Android device: Pixel 4
• Fenix version: 81.1.0-beta.2 (Build #2015761659)

This is what happens when I tap on a downloaded file

This is what happens when I choose Adobe to open the file with

This is what happens when I choose Google drive to open the file with

┆Issue is synchronized with this Jira Task

[eliserichards]

@kglazko @Amejia481

[Amejia481]

@vesta0 it looks like the app that you are using for opening the PDF file doesn't support a file name that long, the message in the second screenshot is from the app. Can you open the file with another app?

[vesta0]

When I locate the file in the Android file browser (see the third screenshot) I can open it in the Adobe reader, Google drive, and even in my Kindle app. These are the same options that are presented by Fenix download manager but neither work when initiated from Fenix.

[Amejia481]

Maybe the Android file browser is shortening the file name 🤔 . Is this a public source(link) where we can test? If not could you please share the full name of the file?

[vesta0]

I just did a demo of the issue with @kglazko

Full file name: agreement_to_receive_notices_electronically.pdf

When opening from the Android default file manager, the files can be opened successfully using the default file browser, adobe, google drive, and kindle.

It seems to be a permissions issue?

[kglazko]

Upon some investigation, I don't know if this has to do with the file name. I created a very, very long-named file seen here: Downloading and opening the file worked with no issue.

An interesting thing to note though is that in Vesta's screenshot, the file icon is a rectangle instead of a document as in my screenshot. That means even though the file is a PDF, it isn't getting categorized as one. Here is an example of the long-named file I used and it was able to open from the prompt seamlessly.

[Willt125]

Seconding this from Daylight, except the file is recognized as a document; either the OS or the browser isn't recognizing itself as an option!

83.1.0 (Build #2015776401)
AC: 63.0.9, fc54c566e
GV: 83.0-20201112153044
AS: 63.0.0

Samsung Galaxy A11
Android 10

[Amejia481]

Very likely to be fixed after mozilla-mobile/android-components#9558 lands similar to #17502

[ebalazs-sv]

Verified as fixed on Nightly 2/19 and Beta 86.0.0-beta.5 from 2/15 with Pixel 2 (Android 9).
I will close this issue and remove the qa:needed label.

[Amejia481]

Thanks @ebalazs-sv !