1925076 - Crash in [@ mozilla.components.support.ktx.android.net.UriKt.isReadable(Uri.kt:204)]

Status: RESOLVED WORKSFORME

(Firefox for Android :: Tabs, defect, P2)

Description

[Noah Bond [:007]]

Trending crash in the Play Console

Based on the full stack trace, it looks like restoring a tab via RestoreUseCase is the thing that invokes this.

First 10 frames:

Exception java.lang.IllegalStateException: Must call PhenotypeContext.setContext() first

at android.os.Parcel.createExceptionOrNull (Parcel.java:3191)
at android.os.Parcel.createException (Parcel.java:3167)
at android.os.Parcel.readException (Parcel.java:3150)
at android.database.DatabaseUtils.readExceptionFromParcel (DatabaseUtils.java:202)
at android.database.DatabaseUtils.readExceptionFromParcel (DatabaseUtils.java:154)
at android.content.ContentProviderProxy.query (ContentProviderNative.java:495)
at android.content.ContentResolver.query (ContentResolver.java:1229)
at android.content.ContentResolver.query (ContentResolver.java:1161)
at android.content.ContentResolver.query (ContentResolver.java:1117)
at mozilla.components.support.ktx.android.net.UriKt.isReadable (Uri.kt:204)

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

:calu, since you are the author of the regressor, bug 1903231, could you take a look?

For more information, please visit BugBot documentation.

Comment 2

[Cathy Lu [:calu]]

Hey QA, can we get steps to reproduce this crash when restoring a local PDF?

I tried opening a local file from My Files in Fenix. When killing Fenix and reopening the app, Fenix correctly logs this RestoreUseCase without crashing:

ContentInputStream: Cannot read the uri: content://media/external/file/1000006519
ContentInputStream: java.lang.SecurityException: org.mozilla.fenix.debug has no access to content://media/external/file/1000006519

I also tried opening a file from Google Drive in Fenix, and when the app is killed, it opens correctly:

ContentInputStream: The uri is readable: content://com.google.android.apps.docs.storage.legacy/enc%3Dencoded%3DncTyJ55ar-oRQRfTcKiGh038haBlaHkHduOx870TPGqOyDlddQrl

Comment 3

[Mira Lobontiu (Android QA)]

Unfortunately, I am unable to trigger the crash following the steps provided in Bug 1903231.
I tested on the latest Fenix Nightly 134.0a1 from 11/18 with the following devices:

• Google Pixel 6 (Android 15),
• Samsung Galaxy Tab S9 Ultra (Android 14),
• Oppo Find X3 Lite (Android 11),
• Samsung Galaxy A14 (Android 14).

I downloaded multiple PDF's, then opened them in Nightly, force closed Fenix, re-opened.
Fenix opened every time without issues and the "content://..." page is displayed correctly.

Comment 4

[Cathy Lu [:calu]]

The crash is no longer showing up on Google Play Console or sentry crashes, closing as Works for me.