android.content.res.Resources$NotFoundException in org.chromium.ui.base.DeviceFormFactor.isTablet

I see in Google Crashlytics crashes only on Samsung devices (S21 SDK 31 and SDK 30)
Occurrences 32 last 30 days.

  at android.content.res.ResourcesImpl.getValue (
  at android.content.res.Resources.getInteger (
  at org.chromium.ui.base.DeviceFormFactor.isTablet (Unknown Source:8)
  at cs.a (Unknown Source:4)
  at org.chromium.content.browser.BrowserStartupControllerImpl.e (Unknown Source:25)
  at org.chromium.content.browser.BrowserStartupControllerImpl.g (Unknown Source:26)
  at (Unknown Source:127)
  at org.chromium.base.ThreadUtils.f (Unknown Source:6)
  at EB0.g (Unknown Source:209)
  at (Unknown Source:7)
  at android.os.Handler.handleCallback (
  at android.os.Handler.dispatchMessage (
  at android.os.Looper.loopOnce (
  at android.os.Looper.loop (
  at (
  at java.lang.reflect.Method.invoke (Native Method)
  at$ (
  at (

I create an Issue

Same crash for me, around 20 crashes / day.
Commenting for visibility, as i don’t have this device to further look into it.
I’m afraid the daily crash count will largely increase with the s20 update as well.

Same for me, around 1000 cases per week.
Have you been using any AD libraries? (Like Google Ad, Appsflyer… etc)

Is there any more information on this issue? I see it in my app too. Initially I saw it ONLY on Samsung S21 phones with Android 12, now I got also a crash report on Crashlytics on one Pixel 3 phone with Android 12, and several on Samsung S21 with Android 11… It happens most often on this call:

String uas = WebSettings.getDefaultUserAgent(context);

I suspect that it happens only if called when no WebView control was created yet, as so far I did not find crashes from similar calls later in the app, when the control was created in it. Surrounding this line with try - catch does not help, as the crash seems to happen in another thread.