Android-components: Saved images can't be opened from the Android taskbar confirmation

Created on 12 Nov 2019  ·  8Comments  ·  Source: mozilla-mobile/android-components

This one is related to a Fenix bug

Steps to reproduce

  1. Navigate to theverge.com
  2. Long tap on one of the featured articles or images
  3. Select "Save image" from the context menu
  4. From the Android taskbar tap on the download confirmation to open the downloaded image

Expected behavior

The image should be opened after tapping the notification

Actual behavior

The downloaded image isn't opened after tapping the notification

Device information

  • Android device:
    • Google Pixel 3a XL (Android 10)
    • Google Pixel 3a XL (Android 9)
    • Huawei Mate 20 Lite (Android 8.1.0)

  • Fenix version:
    • Beta 3.0.0-beta.1 Build #13112229 from 7/11
    • Nightly Build #13120608 from 8/11

Notes

► Video
20191108_124622

<contextmenu> <download> 🐞 bug

All 8 comments

I see a similar problem with PDF files, could you please check if this patch fixes it? Otherwise I'll file a separate issue.

STR is:

  1. Go to http://www.les-enfants-perdus.com/#notre_carte
  2. Click on "Voir la carte".
  3. Click on "Download".
    => a PDF file should be downloaded. Then there's a small notification asking to open it. (BTW this is new, thanks, this is really a nice addition :) )
  4. Click on "Open".
  5. Click on the PDF reader app.
    => PDF app opens with a title null, then closes right away. Same behavior when I click the same item in the notification list.

Thanks!

Hi @julienw, yep, looked into it and it seems it's the same problem with the PDFs.

This fix will also solve our problem here

EDIT: Will retest it after that fix gets merged, as I'm not sure if the filePath will also get fixed there

@BranescuMihai it seems like this is still happening even after that patch 😕

@BranescuMihai, what is the status of the fix for this bug? I am still encountering it in Preview 3.0.0.

I wonder if this is still happening in nightly 🤔

@sblatz: Indeed, it doesn't happen in Nightly anymore. I wonder, though, why Preview 3.0.0 has been released with this unpatched but well known bug. Isn't Preview supposed to be the polished version of Nightly?

@concastinator we do our best to squash as many bugs as we can before each release, but we cannot get to them all. Many bugs we’re aware of have to ship or we’d never launch new stable versions. This was not deemed a release blocker for 3.0 so we moved forward with shipping it.

That being said, since this is fixed in nightly I’m going to throw a QA needed on it to get it closed out!

@sv-ohorvath are you able to verify this has been fixed? :)

Was this page helpful?
0 / 5 - 0 ratings