rare null pointer exception in version 32 in Play Store crash reports

[thestinger]

Exception java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
  at android.os.Parcel.createExceptionOrNull (Parcel.java:3262)
  at android.os.Parcel.createException (Parcel.java:3240)
  at android.os.Parcel.readException (Parcel.java:3223)
  at android.database.DatabaseUtils.readExceptionFromParcel (DatabaseUtils.java:203)
  at android.database.DatabaseUtils.readExceptionWithFileNotFoundExceptionFromParcel (DatabaseUtils.java:166)
  at android.content.ContentProviderProxy.openTypedAssetFile (ContentProviderNative.java:832)
  at android.content.ContentResolver.openTypedAssetFileDescriptor (ContentResolver.java:2043)
  at android.content.ContentResolver.openAssetFileDescriptor (ContentResolver.java:1858)
  at android.content.ContentResolver.openInputStream (ContentResolver.java:1528)
  at app.grapheneos.pdfviewer.PdfViewerScreenKt$createWebViewClient$1.shouldInterceptRequest (PdfViewerScreen.kt:638)
  at WV.tg.a (chromium-SystemWebViewGoogle6432.aab-stable-787104603:103)
  at org.chromium.android_webview.ShouldInterceptRequestMediator.shouldInterceptRequestFromNative (chromium-SystemWebViewGoogle6432.aab-stable-787104603:18)

[ggtlvkma356]

context.contentResolver.openInputStream(pdfUri) normally shall throw one of the four exceptions in current code, but somehow in this case the framework failed to recreate the Exception with createExceptionOrNull, so it returned a null and caused the NPE which is not caught right now.

@inthewaves Shall we just catch the NPE in this case? The likely cause I think is some remote provider failed to resolve for some reason.