mozilla-mobile / fenix Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Crash when downloading Image #6439
Comments
This may be fixed in the newest version of AC, but we haven't gotten new snapshot for Fenix, so maybe it's just because we haven't gotten a new snapshot. |
Corresponding Bugzilla bug filed from crash-stats: https://bugzilla.mozilla.org/show_bug.cgi?id=1595804 |
Let's keep a pulse on this over the next few days but it seems to have disappeared? |
I think the issue is still there, I able to reproduce it on master, the issue happens when the input has an image mime type. STR:
I'm taking a look to how to fix it. I will keep you update. |
I think the main issue rely on feature-prompts and Fenix providers has the same Feature prompts <provider
android:authorities="${applicationId}.fileprovider"
android:name="androidx.core.content.FileProvider"
android:exported="false"
android:grantUriPermissions="true">
<meta-data
android:name="android.support.FILE_PROVIDER_PATHS"
android:resource="@xml/file_paths" />
</provider> Fenix fenix/app/src/main/AndroidManifest.xml Line 252 in 7173bdf
<provider
android:name="androidx.core.content.FileProvider"
android:authorities="${applicationId}.fileprovider"
android:exported="false"
android:grantUriPermissions="true">
<meta-data
android:name="android.support.FILE_PROVIDER_PATHS"
android:resource="@xml/file_paths" />
</provider> |
Found the source of the issue the |
This will fixed after #6699 lands |
Verified as fixed on the latest Nightly 11/25 (#13290608) with Google Pixel 3 (Android Q), and Huawei P9 Lite (Android 7). |
We're getting this new relatively frequent crash:
https://sentry.prod.mozaws.net/operations/fenix-nightly/issues/6580864/
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: