Downloading images from any website is causing com.android.phone to crash
Categories
(Fenix :: Downloads, defect, P1)
Tracking
(firefox117 wontfix, firefox118 verified, firefox119 verified)
People
(Reporter: vedavyas.v696, Assigned: mcarare)
References
Details
(Keywords: crash, Whiteboard: [qa-triaged])
Attachments
(6 files)
User Agent: Mozilla/5.0 (Android 10; Mobile; rv:109.0) Gecko/118.0 Firefox/118.0
Firefox for Android
Steps to reproduce:
Visit any website, long press on am image, save image
Actual results:
Image got saved, Firefox doesn't crash, but weirdly com.android.phone crashes causing a temporary loss of mobile network
Expected results:
No effect on Android Phone application
Comment 1•11 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•11 months ago
|
Comment 2•11 months ago
|
||
Hello!
I was not able to reproduce the issue using the latest Nightly build (118.0a1) from 8th of August 2023. Tested with 2 devices:
Google Pixel 7 Pro (Android 14)
Motorola Moto G9 plus (Android 11)
We would need more information regarding the ticket:
What's the model of the device you were using when you encountered the issue?
Could you send us a video regarding the issue you've faced?
Please see if you still reproduce the issue with other images as well, or maybe, if you can, clear your data before to see if some setting might have interfered with how the image appears.
Thank you!
I'm using Nightly 118.0a1 (Build #2015966755) on Android 10, Samsung Galaxy Note9. In the attached video, I've tried the most generic image and it still crashed the phone app. I also used normal tab, to make sure the issue was not with Private tab.
I'm a bit hesitant to clear data (hopefully the last-resort option) and start setting up from scratch as the settings have worked for me all these months and it takes time to set it all back and it only started crashing very recently. I would be glad to get you the logs if it can't be reproduced elsewhere.
Comment 5•11 months ago
|
||
It would be helpful if you could provide the log.
Have attached the logcat with a crash buffer to minimize the entries. I have a pretty basic understanding of the logcat environment, so if complete logs are required, I will put that up as well
I had a look at the other bug filed as well. And since the bug couldn't be reproduced in either of the two phones mentioned, it could be something limited to earlier version of Android and/or Samsung phones, which could be narrowed once more information from the other bug filee is obtained
Comment 8•11 months ago
•
|
||
Thanks for the log, it looks like the brodcast intent is wrongly captured by CarrierKeyDownloadManager and the brodcast intent contains serializable object which CarrierKeyDownloadManager cannot instantiate the object.
This could be device-specified. Accoring to AOSP , CarrierKeyDownloadManager has a filter and should not receive this intent https://cs.android.com/android/platform/superproject/main/+/main:frameworks/opt/telephony/src/java/com/android/internal/telephony/CarrierKeyDownloadManager.java;l=122-124?q=CarrierKeyDownloadManager&ss=android%2Fplatform%2Fsuperproject%2Fmain
However , it should be Fenix's duty to not contain serializable object in a brodcast intent? Fix maybe either making DownloadState.Status enum Parcelable or passing enum's value in intent.
Anyway I can do that and stop the crash? Or wait for an update?
Comment 10•11 months ago
|
||
I'm not sure. Maybe you could try setting default dialer app to alternative one (like third party dialer).
Since code from Fenix part has been there for a long while ( more than 3 years). i'm not sure why it start causing crash recently.
Does the android os update recently?
Reporter | ||
Comment 11•11 months ago
|
||
I already use Google Dialer, ditching the inbuilt Samsung one
And this phone has reached EOS, so no security updates either. No idea what triggered it all of a sudden
Comment 12•11 months ago
•
|
||
I guess bug 1839366 is the regression of this bug because it changed visibility of intent here https://github.com/mozilla-mobile/firefox-android/commit/1ea20c146103b547820c6204da7022f2d27a7a2c#diff-461a397023312e6d2b9e3969eb2a95e039c43a25a163ab0b35fbbff81cdf2c81L841
Comment 14•11 months ago
|
||
Info from giwayume in bug 1847691 :
This error doesn't happen when I turn off mobile data on the phone and only use wifi, by the way.
and device is Pixel 3a XL
Updated•11 months ago
|
Assignee | ||
Comment 15•11 months ago
|
||
The change made the intent visible for other apps, but it would be the other app's responsibility to correctly handle the received intents that they listen to.
We do use this pattern in other places in the app.
We could limit the broadcast to our own process and that could prevent other apps crashing when not handling the intent extra correctly.
Assignee | ||
Updated•11 months ago
|
Assignee | ||
Updated•11 months ago
|
Comment 16•11 months ago
|
||
Reporter | ||
Comment 17•11 months ago
|
||
Can this build from mentioned git be installed and used or do I need to wait for it to be merged and pushed from play store?
Comment 18•11 months ago
|
||
It could be installed , but not recommend since it will be installed as another Firefox browser: Firefox Fenix (App name) with package name "org.mozilla.fenix.debug"
I'd recommend you to wait for it to be merged.
Updated•11 months ago
|
Reporter | ||
Comment 19•11 months ago
|
||
I did go ahead and install the test build. The crash has stopped and the Firefox Preview logo is really rad!
Updated•11 months ago
|
Comment 20•11 months ago
|
||
I have a same issue on Sony Xperia XZ2 (Android 10) device.
Comment hidden (spam) |
Comment hidden (spam) |
Comment 24•10 months ago
|
||
Authored by https://github.com/mcarare
https://github.com/mozilla-mobile/firefox-android/commit/724f9a64ed42fe11f4c3c88b1e433df09cc3b6ee
[main] Bug 1847141 - Suppress UnspecifiedRegisterReceiverFlag for SDK < 33
Authored by https://github.com/mcarare
https://github.com/mozilla-mobile/firefox-android/commit/24947fe28fe8fb5037403ac807923f1d2b2ebfff
[main] Bug 1847141 - Restrict receiving download broadcasts.
Comment 25•10 months ago
|
||
Verified as fixed on the latest Fenix Nightly 119.0a1 from 9/6 with Sony Xperia Z5 Premium (Android 7.1.1).
I was able to reproduce the issue on the RC 117.0 build with the same device.
Updated•10 months ago
|
Comment 26•10 months ago
|
||
The patch landed in nightly and beta is affected.
:mcarare, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval. Also, don't forget to request an uplift for the patches in the regression caused by this fix.
- If no, please set
status-firefox118
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•10 months ago
|
Updated•10 months ago
|
Comment 27•10 months ago
|
||
Updated•10 months ago
|
Comment 28•10 months ago
|
||
Authored by https://github.com/mcarare
https://github.com/mozilla-mobile/firefox-android/commit/6f0165bdee10df149229434713fb4321708693bf
[main] Bug 1847141 - Remove hardcoding of RECEIVE_DOWNLOAD_BROADCAST_PERMISSION
Comment 30•10 months ago
|
||
Hello devs, i think this bug is important enough to require an uplift. Because this bug causes users' phone Celular network down. It is quite a serious issue.
Updated•10 months ago
|
Assignee | ||
Updated•10 months ago
|
Comment 32•10 months ago
|
||
This fix already caused a pretty severe regression (which yesterday's follow-up fixed). I agree that the impact of this bug probably warrants a backport to v118, though. Let's give it a bit more time to bake and then we can revisit. Thanks for following up, jackyzy823!
Comment 34•10 months ago
|
||
Last beta builds today, Mihai is that a wontfix for 118?
Assignee | ||
Comment 35•10 months ago
•
|
||
My opinion is that a backport is risky at this point. The issue caused by the initial fix seemed worse ( not being able to update the app) than the current issue, also taking into consideration the small number of reports. Is a future dot release planned? Could this be included at that point?
Comment 36•10 months ago
|
||
We have a planned dot release mid-cycle.
Assignee | ||
Comment 37•10 months ago
|
||
Then I think we should consider adding this to that dot release, if no further issues are reported for the current fix.
Comment 38•10 months ago
|
||
This should be left as fix-optional then. If it's set to wontfix, it won't appear in any bug queries down the road.
Comment 41•10 months ago
|
||
Assignee | ||
Comment 42•10 months ago
|
||
Comment on attachment 9354502 [details] [review]
[mozilla-mobile/firefox-android] Bug 1847141 - Restrict receiving download broadcasts. (#3746)
Beta/Release Uplift Approval Request
- User impact if declined: Some devices might have issues as apps try to handle the broadcast intent from Firefox and fail to do so. This fix prevents other apps from receiving the broadcast.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky):
- String changes made/needed:
- Is Android affected?: Yes
Comment 44•9 months ago
|
||
Comment on attachment 9354502 [details] [review] [mozilla-mobile/firefox-android] Bug 1847141 - Restrict receiving download broadcasts. (#3746) Although this is evaluated as medium risk, this was verified on nightly, is now on beta and no new regressions were reported, let's take it into our next Android dot release, thanks.
Comment 45•9 months ago
|
||
Authored by https://github.com/mcarare
https://github.com/mozilla-mobile/firefox-android/commit/32491a2824dab037f67ac9c38b3b96c17953422e
[releases_v118] Bug 1847141 - Restrict receiving download broadcasts by other apps
Comment 46•9 months ago
|
||
I was not able to trigger a crash by downloading images on several websites.
Tested on the lates RC 118.1.1 build 1 with Sony Xperia Z5 Premium (Android 7.1.1).
Description
•