Bug 1971417 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

### Steps to reproduce
1. Start a streamed download (any live.log for a task that is still ongoing on https://treeherder.mozilla.org/jobs?repo=try)
2. Click on the details button on the download in progress snackbar or go to the downloads screen through the menu

There's another way that I can notice that live downloads are not showing up on the download screen:
1. Start any download
2. Make the download fail by turning WiFi off, for example
3. Click on the details button on the download failed snackbar or go to the downloads screen through the menu

### Expected behavior
The download should be visible as downloading.

In the second case, the download should be visible as failed.

### Actual behavior
The download is not visible as downloading until after a while, despite the system notification already showing the file as downloading

In the second case, the failed download initially shows up but then disappears almost instantly

### Device information

* Android device model: Samsung A35
* Android OS version: Android 14

### Any additional information
Commenting out [this line](https://searchfox.org/mozilla-central/rev/b6a437e0e51dbbfa65f07ee4e1db3864624ab5ea/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/downloads/listscreen/middleware/DownloadUIMapperMiddleware.kt#65) will sometimes cause the expected behaviour. You may also need to kill fenix between attempts to get the unexpected behaviour that this bug is reporting
### Steps to reproduce
1. Start a streamed download (any live.log for a task that is still ongoing on https://treeherder.mozilla.org/jobs?repo=try)
2. Click on the details button on the download in progress snackbar or go to the downloads screen through the menu

There's another way that I can notice that live downloads are not showing up on the download screen:
1. Start any download
2. Make the download fail by turning WiFi off, for example
3. Click on the details button on the download failed snackbar or go to the downloads screen through the menu

### Expected behavior
The download should be visible as downloading.

In the second case, the download should be visible as failed.

### Actual behavior
The download is not visible as downloading until after a while, despite the system notification already showing the file as downloading. Sometimes, the download initially shows up but then disappears almost instantly. The latter is what happens for the download failed case

### Device information

* Android device model: Samsung A35
* Android OS version: Android 14

### Any additional information
Commenting out [this line](https://searchfox.org/mozilla-central/rev/b6a437e0e51dbbfa65f07ee4e1db3864624ab5ea/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/downloads/listscreen/middleware/DownloadUIMapperMiddleware.kt#65) will sometimes cause the expected behaviour. You may also need to kill fenix between attempts to get the unexpected behaviour that this bug is reporting
### Steps to reproduce
1. Start a streamed download (any live.log for a task that is still ongoing on https://treeherder.mozilla.org/jobs?repo=try)
2. Click on the details button on the download in progress snackbar or go to the downloads screen through the menu

### Expected behavior
The download should be visible as downloading.

### Actual behavior
The download is not visible as downloading until after a while, despite the system notification already showing the file as downloading. Sometimes, the download initially shows up but then disappears almost instantly.

### Device information

* Android device model: Samsung A35
* Android OS version: Android 14

### Any additional information
Commenting out [this line](https://searchfox.org/mozilla-central/rev/b6a437e0e51dbbfa65f07ee4e1db3864624ab5ea/mobile/android/fenix/app/src/main/java/org/mozilla/fenix/downloads/listscreen/middleware/DownloadUIMapperMiddleware.kt#65) will sometimes cause the expected behaviour. You may also need to kill fenix between attempts to get the unexpected behaviour that this bug is reporting

Back to Bug 1971417 Comment 0