IssueTracker

Any fix planned ?

Can u give me info of tablet ? I know who had it unlocked with my info on
it ! I'll make sure I thank her later,thanks for the info.if there anything
I can help this group within here if I can help,keep me in mind !
E.C.
C.h.e.s.
ecastillo041979@gmail.com

On Wed, May 26, 2021, 6:44 AM <buganizer-system@google.com> wrote:

It is not only for tablets. It is for any devices

Fatal Exception: android.content.res.Resources$NotFoundException: Resource ID #0x20c0016
       at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:239)
       at android.content.res.MiuiResourcesImpl.getValue(MiuiResourcesImpl.java:96)
       at android.content.res.Resources.getInteger(Resources.java:1209)
       at org.chromium.ui.base.DeviceFormFactor.isTablet(DeviceFormFactor.java:2)
       at mo.a(mo.java:2)
       at org.chromium.content.browser.BrowserStartupControllerImpl.e(BrowserStartupControllerImpl.java:8)
       at org.chromium.content.browser.BrowserStartupControllerImpl.g(BrowserStartupControllerImpl.java:5)
       at c7.run(c7.java:23)
       at org.chromium.base.ThreadUtils.f(ThreadUtils.java:2)
       at as0.i(as0.java:31)
       at Zr0.run(Zr0.java:2)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:236)
       at android.app.ActivityThread.main(ActivityThread.java:7861)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:600)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:967)

Also a lot of crashes

There are more and more crashes

Fatal Exception: android.content.res.Resources$NotFoundException: Resource ID #0x20c0016
       at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:285)
       at android.content.res.Resources.getInteger(Resources.java:1297)
       at org.chromium.ui.base.DeviceFormFactor.isTablet(DeviceFormFactor.java:2)
       at Bp.a(Bp.java:2)
       at org.chromium.content.browser.BrowserStartupControllerImpl.e(BrowserStartupControllerImpl.java:8)
       at org.chromium.content.browser.BrowserStartupControllerImpl.g(BrowserStartupControllerImpl.java:5)
       at R7.run(R7.java:23)
       at org.chromium.base.ThreadUtils.f(ThreadUtils.java:2)
       at av0.i(av0.java:35)
       at Zu0.run(Zu0.java:2)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:246)
       at android.app.ActivityThread.main(ActivityThread.java:8512)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)

WebView's resources are dynamically added to your app when you load WebView. Unfortunately there are a number of ways for this to be "lost" if your app is doing unsupported things with Context and Resources objects, either in your own code or in libraries you are using.

If you're using Resources.updateConfiguration, or creating instances or subclasses of Resources yourself, or wrapping Contexts in complex ways, this is likely to be the cause. For some use cases you can use Context.createConfigurationContext to override configuration parameters for a given context - this won't cause issues with WebView. There's a wide range of different things apps might be doing here unfortunately, so it's very difficult to offer specific advice.

I am using only createConfigurationContext a long time, and not changed anything in this code.
I am not use any other ways for wrap Resources or Context.

    override fun attachBaseContext(base: Context) {
        val overrideConfig = Configuration()
        overrideConfig.setLocale(currentLocale)
        updateSystemDefaultLocale(currentLocale)
        applyOverrideConfiguration(overrideConfig)
        super.attachBaseContext(base.createConfigurationContext(overrideConfig))
    }

Also, I can see that the WebView is using resources from the Application Context. I don't change anything in the context of the application, only in the Activity Base context.

https://source.chromium.org/chromium/chromium/src/+/main:ui/android/java/src/org/chromium/ui/base/DeviceFormFactor.java;l=46?q=DeviceFormFactor&ss=chromium

And I haven;t any other problems/crashes with Resources

It might be some library you are using; unfortunately it's very difficult to track this down. One other possible cause we've seen is users with rooted devices running custom theme engines that apply to all their apps, in which case it's not something you can do anything about at all, but that should be pretty uncommon.

For the vast majority of apps WebView is the only thing that dynamically changes the AssetManager configuration for your app, since the APIs to do so aren't public, so it's usually going to be the case that this interaction with WebView is the only problem you will see and resources will otherwise work. :(

Unless you have a way to reliably reproduce this, which I presume you don't if it's just being reported in crashlytics, then there's not really anything we can do here. We have investigated this in detail several times before and when we've been able to determine the cause it has always been an unsupported manipulation of Resources/Context in the app's code/libraries.

Here's some other things I would try to check that have sometimes been useful pointers before:

- What Context object are you passing to WebView's constructor? Is it your Activity, or something else?
- Does that context return the same object for getAssets() and getResources().getAssets()?
- What does getApplicationContext() return on that context object? Is it your Application object, or something else?
- What do you call in Application.attachBaseContext() if anything? Do any of the things you call operate on the Context at all, even if they aren't wrapping it?

From the graphs you attached it looks like this is happening primarily on Android 11 devices from Xiaomi - is that a reflection of your app's userbase, or is that unusual? Do other unrelated crashes also have that kind of distribution, or not?