DayNight theme is changed when WebView is inflated [37124582]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Oct 25, 2016 02:49PM

Library used: appcompat-v7
Version used: 25.0.0
Theme used: Theme.AppCompat.DayNight
Devices/Android versions reproduced on: Nexus 5x, Nexus 6 - Android 7.0

The activity containing a WebView is recreated (from onStart() method) because uiMode is changed when WebView is being created (inside its constructor). This only happens on the first WebView inflation.

Steps to reproduce this bug:

1º - Set the default night mode to AppCompatDelegate.MODE_NIGHT_YES on application class.
2º - Add a WebView to layout file (in the attached example a CustomWebView has been created only for logs purposes, common WebView has the same effect).
3º - Launch the app and the activity is recreated.

In appcompat-v7 versions previous to 24.2.0 the activity is not recreated but the uiMode is changed too.

Here some logs from:

Main: Before onCreate super() - Mode night active: false
Main: After onCreate super() - Mode night active: true
CustomWebView: Before constructor super() - Mode night active: true
CustomWebView: After constructor super() - Mode night active: false
Main: Before onCreate super() - Mode night active: false
Main: After onCreate super() - Mode night active: true
CustomWebView: Before constructor super() - Mode night active: true
CustomWebView: After constructor super() - Mode night active: true

DayNightTheme.zip

482 KB

Download

Comments

mi...@gmail.com <mi...@gmail.com> #2Oct 25, 2016 02:56PM

In SystemJobService, it can expect null, and able to tolerance null from WorkManagerImpl.getInstance, due to auto-backup reason.

@Override
public void onCreate() {
super.onCreate();
mWorkManagerImpl = WorkManagerImpl.getInstance(getApplicationContext());
if (mWorkManagerImpl == null) {
// This can occur if...
// 1. The app is performing an auto-backup. Prior to O, JobScheduler could erroneously
// try to send commands to JobService in this state (

b/32180780

). Since neither
// Application#onCreate nor ContentProviders have run, WorkManager won't be
// initialized. In this case, we should ignore all JobScheduler commands and tell it
// to retry.
But, current WorkManagerImpl.getInstance(Context context) implementation is that, it will never return null but throw IllegalStateException.

Isn't there's conflict among these 2 SystemJobService.onCreate logic, and WorkManagerImpl.getInstance logic?

ch...@google.com <ch...@google.com> #3Jan 11, 2017 12:43AM

Assigned to ch...@google.com.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit e14104eb7008f82edd50b37e16bd119b307e0554
Author: Sumir Kataria <sumir@google.com>
Date: Mon Jun 24 10:50:57 2019

Fix for JobScheduler calls when backup is in progress.

The original fix (ag/Ia1604b7c4b98f6b31869e1161a0c1efce7fe46f2) relied
on a null-check, but the new version of WorkManager.getInstance(Context)
with the Context param doesn't return null; it throws an Exception. This
CL updates the three places where we explicitly check for the return value
internally:

1. SystemJobService (the main place where this would manifest)
2. RescheduleReceiver
3. WorkManagerTestInitHelper (for consistency)

Fixes: 135858602
Test: Ran existing tests
Change-Id: Ia232869712d0c78fd80e91d0a863b8c50a080400

M work/workmanager-testing/src/main/java/androidx/work/testing/WorkManagerTestInitHelper.java
M work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/RescheduleReceiver.java
M work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobService.java

https://android-review.googlesource.com/988026

https://goto.google.com/android-sha1/e14104eb7008f82edd50b37e16bd119b307e0554

mn...@gmail.com <mn...@gmail.com> #4Jan 11, 2017 03:01PM

Thanks you so much for the speedy fixed!

May I know when will it be ready for production? As, currently, this IllegalStateException is impacting our users.

ch...@google.com <ch...@google.com> #5Jan 11, 2017 03:10PM

Hello, please look for this later in the week. If you want to work around this bug specifically and don't need on-demand initialization, you can use the old (deprecated) WorkManager.getInstance() method for now.

mn...@gmail.com <mn...@gmail.com> #6Jan 11, 2017 03:12PM

Hello. Thanks for respond. I surely will keep a pair of eye on the next release :)

Yes. We don't need on-demand initialization. May I know how does using old (deprecated) WorkManager.getInstance() in our app code, able to bypass this problem? Isn't the crash is origin from library internal SystemJobService?

We once thinking to bypass this problem, by switching back to Version 2.0.1 (The version just before WorkManager.getInstance(Context) is introduced). However, we notice Room version is being changed in between. Downgrading WorkManager version, might cause additional SQLite problem.

jo...@nuzzel.com <jo...@nuzzel.com> #7May 23, 2017 06:12AM

Sorry, you are correct that moving to the deprecated method will not help you here. I would advise waiting for the release later this week. And thank you very much for finding this bug and doing the research to find the underlying issue.

I am curious: do you actually have reports of this bug on Android 9? It should've been fixed in the platform layer at that point. If possible, can you share any Android 9 specific logs/bugreports/stacktraces with device models?

ch...@google.com <ch...@google.com> May 23, 2017 08:16AM

Reassigned to ki...@google.com.

mn...@gmail.com <mn...@gmail.com> #8May 23, 2017 05:04PM

OK. Finger crossed users will not leave our app. I will follow the Green Dinosaur in Twitter, to wait for his announcement.

Based on your code comment, I thought this problem shouldn't occur in new Android but it happens some how. This is the log

Asus ZenFone 5 (ZE620KL) (ASUS_X00QD), Android 9 (Happen 2 times)
Asus ZenFone 5Z (ZS620KL/ZS621KL) (ASUS_Z01R_1), Android 9 (Happen 1 time)

3 incidents are having same log trace as below

java.lang.RuntimeException:
at android.app.ActivityThread.handleCreateService (ActivityThread.java:3570)
at android.app.ActivityThread.access$1300 (ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1672)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:198)
at android.app.ActivityThread.main (ActivityThread.java:6732)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)
Caused by: java.lang.IllegalStateException:
at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:142)
at androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:53)
at android.app.ActivityThread.handleCreateService (ActivityThread.java:3558)
at android.app.ActivityThread.access$1300 (ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1672)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:198)
at android.app.ActivityThread.main (ActivityThread.java:6732)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

I attach the screenshot of Google Play Console as well. (I expect the stack trace should print programmer's message side-by-side with IllegalStateException. But it doesn't)

Feel free to let me know if you need any information from my side. Happy to help.

ki...@google.com <ki...@google.com> #9May 23, 2017 07:09PM

Reassigned to al...@google.com.

Thanks, we'll investigate this internally.

al...@google.com <al...@google.com> #10May 23, 2017 07:32PM

Reassigned to ch...@google.com.

Hello, wondering whether the fix will be released in another one, or two days. As, users start to complain and leaving our app, due to increased crash rate :(

Thanks.

al...@google.com <al...@google.com> #11May 23, 2017 07:56PM

Hi, we're still aiming to get this out this week.

ki...@google.com <ki...@google.com> #12May 23, 2017 08:02PM

still have bug:

trace:
5 java.lang.IllegalStateException:WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
6 androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService.java:68)
7 android.app.ActivityThread.handleCreateService(ActivityThread.java:3133)
8 android.app.ActivityThread.access$1900(ActivityThread.java:196)
9 android.app.ActivityThread$H.handleMessage(ActivityThread.java:1622)
10 com.android.tony.defenselib.hook.HookHandle$1.handleMessage(HookHandle.java:30)
11 android.os.Handler.dispatchMessage(Handler.java:107)
12 android.os.Looper.loop(Looper.java:210)
13 android.app.ActivityThread.main(ActivityThread.java:5982)
14 java.lang.reflect.Method.invoke(Native Method)
15 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:852)
16 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:742)

this code cause crash:

if (!Application.class.equals(getApplication().getClass())) {
// During auto-backup, we don't get a custom Application subclass. This code path
// indicates we are either performing auto-backup or the user never used a custom
// Application class (or both).
throw new IllegalStateException("WorkManager needs to be initialized via a "
+ "ContentProvider#onCreate() or an Application#onCreate().");
}

my analysis:

code in handleCreateService() in ActivityThread.java:
" Application app = packageInfo.makeApplication(false, mInstrumentation);
service.attach(context, this,

data.info.name, data.token, app, ActivityManager.getService())
"

handleCreateService--->. Application app = packageInfo.makeApplication(false, mInstrumentation); ---> forceDefaultAppClass is always false-->if have custom Application,will make custom Application ---> service.attach(context, this,

data.info.name, data.token, app, ActivityManager.getService()); ---> so getApplication() in service get custom application
--> if have customApplication, the code : "Application.class.equals(getApplication().getClass()" in Service will be false , even it's in backup mode

nightmodeTabsNotStyled.png

143 KB

View

Download

mn...@gmail.com <mn...@gmail.com> #13May 23, 2017 08:14PM

i'm also having the same crash, here is the relevant stacktrace:

compileSdkVersion 30
implementation 'androidx.work:work-runtime-ktx:2.4.0'

Crash
TCT (Alcatel) 5056D
Android 6.0 (SDK 23)
48.aab
2 hours ago

java.lang.RuntimeException:
at android.app.ActivityThread.handleCreateService (ActivityThread.java:2887)
at android.app.ActivityThread.access$1900 (ActivityThread.java:150)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1427)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:148)
at android.app.ActivityThread.main (ActivityThread.java:5417)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:616)
Caused by: java.lang.IllegalStateException:
at androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:2)
at android.app.ActivityThread.handleCreateService (ActivityThread.java:2877)
at android.app.ActivityThread.access$1900 (ActivityThread.java:150)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1427)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:148)
at android.app.ActivityThread.main (ActivityThread.java:5417)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:616)

What could the walkaround this issue? Is there another way to initialize the WorkManager instance? I'm using

private fun getWorkManager(): WorkManager =
try {
WorkManager.getInstance(App.context)
} catch (e: Exception) {
e.printStackTrace()
sleep(100)
getWorkManager()
}

ki...@google.com <ki...@google.com> #14May 23, 2017 08:16PM

Same Error on production when call WorkManager.getInstance(context):
Library version: androidx.work:work-runtime:2.4.0

Samsung Galaxy S8 (dreamlte), 3840MB RAM, Android 9

java.lang.RuntimeException:
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6227)
at android.app.ActivityThread.access$1200 (ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1785)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:214)
at android.app.ActivityThread.main (ActivityThread.java:7050)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:494)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965)

Caused by: java.lang.IllegalStateException:
at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:150)
at androidx.work.WorkManager.getInstance (WorkManager.java:184)
at br.com.rcgm.dicaslotofacilfull.task.WorkRequestSincronizarConcurso.enfileirar (WorkRequestSincronizarConcurso.java:20)
at br.com.rcgm.dicaslotofacilfull.BaseApplication.onCreate (BaseApplication.java:23)
at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1154)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6222)

mn...@gmail.com <mn...@gmail.com> #15May 23, 2017 08:19PM

Hi,

I'm also facing same issue, in few devices.

Instance access : WorkManager.getInstance()
I'm not doing on-demand Initialization.
version used: 'androidx.work:work-runtime:2.3.4'

Device details
Brand: samsung
Model: Galaxy J2 Pro
Android version: 6.0.1

Fatal Exception: java.lang.RuntimeException: Unable to create service androidx.work.impl.background.systemjob.SystemJobService: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3883)
at android.app.ActivityThread.-wrap8(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1909)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:7325)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
Caused by java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
at androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService.java:73)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3873)
at android.app.ActivityThread.-wrap8(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1909)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:7325)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

ki...@google.com <ki...@google.com> #16May 23, 2017 08:24PM

i have the same issue

mn...@gmail.com <mn...@gmail.com> #17May 23, 2017 08:26PM

deleted

ch...@google.com <ch...@google.com> #18May 25, 2017 09:47AM

Still seeing this issue in 2.5.0 using default WorkManager.getInstance() initialization. How can we prevent this situation from occurring?

if (!Application.class.equals(getApplication().getClass())) {
// During auto-backup, we don't get a custom Application subclass. This code path
// indicates we are either performing auto-backup or the user never used a custom
// Application class (or both).
throw new IllegalStateException("WorkManager needs to be initialized via a "
+ "ContentProvider#onCreate() or an Application#onCreate().");
}

mn...@gmail.com <mn...@gmail.com> #19May 25, 2017 09:48AM

this issue on workManager 2.5.0 when initialize WorkManager in background thread, bring it back to UI thread

ch...@google.com <ch...@google.com> Aug 29, 2017 07:17AM

Reassigned to ki...@google.com.

ki...@google.com <ki...@google.com> Sep 7, 2018 06:50PM

Reassigned to ch...@google.com.

[Deleted User] <[Deleted User]> #20Sep 11, 2018 04:19PM

I begin to see this issue after using "on demand Initialization"

Stacktrace:
Caused by java.lang.IllegalStateException
WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:73)
android.app.ActivityThread.handleCreateService (ActivityThread.java:3833)
android.app.ActivityThread.access$1500 (ActivityThread.java:229)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loop (Looper.java:226)
android.app.ActivityThread.main (ActivityThread.java:7178)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:503)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:942)

For now, the device affected is
android 9 Realme.

Work Manager version: 2.6.0

da...@gmail.com <da...@gmail.com> #21Sep 12, 2018 06:10AM

Still happening with WorkManager 2.7.1 Samsung Galaxy S21 Ultra 5G Android 12 (SDK 31)

java.lang.RuntimeException: 
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4953)
  at android.app.ActivityThread.access$1900 (ActivityThread.java:310)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2300)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8669)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)
Caused by: java.lang.IllegalStateException: 
  at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:158)
  at androidx.work.impl.foreground.SystemForegroundDispatcher.<init> (SystemForegroundDispatcher.java:105)
  at androidx.work.impl.foreground.SystemForegroundService.initializeDispatcher (SystemForegroundService.java:96)
  at androidx.work.impl.foreground.SystemForegroundService.onCreate (SystemForegroundService.java:59)
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4940)
  at android.app.ActivityThread.access$1900 (ActivityThread.java:310)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2300)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8669)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)

ch...@google.com <ch...@google.com> #22Jan 30, 2019 04:50AM

We recently moved our WorkManager initialization to the default pattern and have started seeing this same issue.

java.lang.RuntimeException: Unable to create service androidx.work.impl.background.systemjob.SystemJobService: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
        at android.app.ActivityThread.handleCreateService(ActivityThread.java:5073)
        at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2425)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8741)
        at java.lang.reflect.Method.invoke(Method.java:-2)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

Caused by: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
        at androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService:73)
        at android.app.ActivityThread.handleCreateService(ActivityThread.java:5060)
        at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2425)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8741)
        at java.lang.reflect.Method.invoke(Method.java:-2)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

ch...@google.com <ch...@google.com> #23Feb 10, 2019 10:57PM

Marked as fixed.

I would check to make sure that the app is not a multi-process app. If it is, you will need your Application to additionally sub-class Configuration.Provider or additionally define a second provider for the other process.

xw...@gmail.com <xw...@gmail.com> #24Feb 13, 2019 09:52AM

Hi all, I am also facing the same crash in Work Manager 2.7.1 with on-demand initialization in Samsung X-Cover Pro(31), sdk 32. There's no concrete scenario for this crash to happen, it happens randomly at any screen. Plus the auto-backup is disabled in my app which was listed as one of the factors responsible for the crash. Can someone please assist me with a way to fix/handle this crash?

ja...@gmail.com <ja...@gmail.com> #25Feb 25, 2019 08:08PM

Hi all , i use workManager 2.7.0 face some crash "IllegalStateExceptionWorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate()" . i am sure app manifest allowBackUp=false and initWorkManger in every process. Can someone please assist me with a way to fix/handle this crash?

ch...@google.com <ch...@google.com> #26Feb 25, 2019 08:34PM

I'm experience the same problem. I used suspend function to init WorkManager and used Dispatchers.Default as a scope to launch. I'm going to use runBlocking instead

ja...@gmail.com <ja...@gmail.com> #27Feb 25, 2019 09:11PM

Perfect, thanks!

ja...@gmail.com <ja...@gmail.com> #28Mar 14, 2019 05:37PM

Seems to be working for me

ch...@google.com <ch...@google.com> #29Mar 14, 2019 08:33PM

Awesome, closing this as AppCompat v1.1.0-alpha03 was released yesterday.

mi...@dailymotion.com <mi...@dailymotion.com> #30Nov 26, 2019 02:11PM

Hi I'm using the appcompat 1.1.0, and I get this issue on a Pixel 3
Instantiating a WebView after setDefaultNightMode, revert to my default theme.

Putting WebView(this) before setDefaultNightMode is a (ugly) workaround for the moment.

Do you have some news about that ?

Thanks

ro...@gmail.com <ro...@gmail.com> #31Jan 19, 2020 02:30PM

When will this be fixed? Still doesn't work with appcompat 1.2.0 alpha versions.

ga...@gmail.com <ga...@gmail.com> #32Apr 10, 2020 03:37AM

When will this be fixed? Still doesn't work with appcompat 1.2.0 alpha versions.

xj...@gmail.com <xj...@gmail.com> #33May 24, 2020 10:48PM

1.2.0-rc01 issue still here ...

[Deleted User] <[Deleted User]> #34Aug 6, 2020 03:10AM

After about 2 years I come back this thread again. The issue still happens when I used native advance ads when using appcompat 1.2.0 and 1.3.0-apha01.

The only way to resolve this problem that still init a dummy WebView in Application before set night theme

[Deleted User] <[Deleted User]> #35Aug 18, 2020 03:34AM

1.2.0 issue still here ...

[Deleted User] <[Deleted User]> #36Aug 28, 2020 10:48AM

Hey! You should try custom config workaround.

https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:appcompat/appcompat/src/androidTest/java/androidx/appcompat/testutils/BaseTestActivity.java;l=89-104?q=BaseTestActivity&ss=androidx%2Fplatform%2Fframeworks%2Fsupport

This is the suggestion.

https://www.reddit.com/r/androiddev/comments/idefss/were_on_the_engineering_team_for_android_jetpack/g3263de?utm_source=share&utm_medium=web2x&context=3

kr...@gmail.com <kr...@gmail.com> #37Oct 8, 2020 09:12AM

reopen this issue here

https://issuetracker.google.com/issues/170328697

ca...@seadowg.com <ca...@seadowg.com> #38Aug 30, 2021 03:32PM

Still seeing this problem with appcompat 1.3.1. Constructing a dummy WebView before forcing night mode acts as a workaround (as described earlier in this thread). This should be reopened I think.

sl...@pentacomp.pl <sl...@pentacomp.pl> #39Apr 26, 2022 08:44AM

This issue is still present, using appcompat 1.4.0 here

ta...@gmail.com <ta...@gmail.com> #40Sep 22, 2022 05:39PM

This issue is still present, using appcompat 1.6.0-rc01

ki...@google.com <ki...@google.com> Sep 22, 2022 05:48PM

Reassigned to al...@google.com.

al...@google.com <al...@google.com> Sep 22, 2022 06:41PM

Reassigned to an...@google.com.

dm...@gmail.com <dm...@gmail.com> #41Feb 1, 2023 08:17AM

The issue is still present, using appcompat 1.5.1

da...@grupoasesores.com.mx <da...@grupoasesores.com.mx> #42Mar 28, 2023 03:31AM

Still present nowdays... as a work around I've made this as suggested by ch...@google.com

protected void onCreate(Bundle savedInstanceState) {
if (Build.VERSION.SDK_INT >= 24) {
new WebView(this);
}
super.onCreate(savedInstanceState);
}

It's weird but it works.

FYI: I'm developing a multi fragment application with only one MainActivity, so I had to implement this one-time and that fixed the UiMode issue.

pu...@gmail.com <pu...@gmail.com> #43Sep 21, 2023 11:18AM

This is still an issue using Theme.Material3.DayNight from latest material-components-android, but only on Android 10 devices and below. This is particularly annoying when using AdMob. The ugly workaround to instantiate a WebView prior to calling AppCompatDelegate#setDefaultNightMode still work for these devices:

        int nightMode = ...;

	
	if (nightMode != AppCompatDelegate.MODE_NIGHT_NO &&  Build.VERSION.SDK_INT <= Build.VERSION_CODES.Q) {
		try {
			new WebView(getApplicationContext());
		} catch (Exception ignored) {
		}
	}

	AppCompatDelegate.setDefaultNightMode(nightMode);

Message last modified on Sep 21, 2023 11:27AM

ab...@gmail.com <ab...@gmail.com> #44Dec 16, 2024 01:35PM

Still present, using androidx.appcompat:appcompat:1.7.0 and the hack "new WebView(this);" still works

Issue 37124582

Description

Issue summary

Comments

mi...@gmail.com <mi...@gmail.com> #2Oct 25, 2016 02:56PM

ch...@google.com <ch...@google.com> #3Jan 11, 2017 12:43AM

mn...@gmail.com <mn...@gmail.com> #4Jan 11, 2017 03:01PM

ch...@google.com <ch...@google.com> #5Jan 11, 2017 03:10PM

mn...@gmail.com <mn...@gmail.com> #6Jan 11, 2017 03:12PM

jo...@nuzzel.com <jo...@nuzzel.com> #7May 23, 2017 06:12AM

ch...@google.com <ch...@google.com> May 23, 2017 08:16AM

mn...@gmail.com <mn...@gmail.com> #8May 23, 2017 05:04PM

ki...@google.com <ki...@google.com> #9May 23, 2017 07:09PM

al...@google.com <al...@google.com> #10May 23, 2017 07:32PM

al...@google.com <al...@google.com> #11May 23, 2017 07:56PM

ki...@google.com <ki...@google.com> #12May 23, 2017 08:02PM

mn...@gmail.com <mn...@gmail.com> #13May 23, 2017 08:14PM

ki...@google.com <ki...@google.com> #14May 23, 2017 08:16PM

mn...@gmail.com <mn...@gmail.com> #15May 23, 2017 08:19PM

ki...@google.com <ki...@google.com> #16May 23, 2017 08:24PM

mn...@gmail.com <mn...@gmail.com> #17May 23, 2017 08:26PM

ch...@google.com <ch...@google.com> #18May 25, 2017 09:47AM

mn...@gmail.com <mn...@gmail.com> #19May 25, 2017 09:48AM

ch...@google.com <ch...@google.com> Aug 29, 2017 07:17AM

ki...@google.com <ki...@google.com> Sep 7, 2018 06:50PM

[Deleted User] <[Deleted User]> #20Sep 11, 2018 04:19PM

da...@gmail.com <da...@gmail.com> #21Sep 12, 2018 06:10AM

ch...@google.com <ch...@google.com> #22Jan 30, 2019 04:50AM

ch...@google.com <ch...@google.com> #23Feb 10, 2019 10:57PM

xw...@gmail.com <xw...@gmail.com> #24Feb 13, 2019 09:52AM

ja...@gmail.com <ja...@gmail.com> #25Feb 25, 2019 08:08PM

ch...@google.com <ch...@google.com> #26Feb 25, 2019 08:34PM

ja...@gmail.com <ja...@gmail.com> #27Feb 25, 2019 09:11PM

ja...@gmail.com <ja...@gmail.com> #28Mar 14, 2019 05:37PM

ch...@google.com <ch...@google.com> #29Mar 14, 2019 08:33PM

mi...@dailymotion.com <mi...@dailymotion.com> #30Nov 26, 2019 02:11PM

ro...@gmail.com <ro...@gmail.com> #31Jan 19, 2020 02:30PM

ga...@gmail.com <ga...@gmail.com> #32Apr 10, 2020 03:37AM

xj...@gmail.com <xj...@gmail.com> #33May 24, 2020 10:48PM

[Deleted User] <[Deleted User]> #34Aug 6, 2020 03:10AM

[Deleted User] <[Deleted User]> #35Aug 18, 2020 03:34AM

[Deleted User] <[Deleted User]> #36Aug 28, 2020 10:48AM

kr...@gmail.com <kr...@gmail.com> #37Oct 8, 2020 09:12AM

ca...@seadowg.com <ca...@seadowg.com> #38Aug 30, 2021 03:32PM

sl...@pentacomp.pl <sl...@pentacomp.pl> #39Apr 26, 2022 08:44AM

ta...@gmail.com <ta...@gmail.com> #40Sep 22, 2022 05:39PM

ki...@google.com <ki...@google.com> Sep 22, 2022 05:48PM

al...@google.com <al...@google.com> Sep 22, 2022 06:41PM

dm...@gmail.com <dm...@gmail.com> #41Feb 1, 2023 08:17AM

da...@grupoasesores.com.mx <da...@grupoasesores.com.mx> #42Mar 28, 2023 03:31AM

pu...@gmail.com <pu...@gmail.com> #43Sep 21, 2023 11:18AM

ab...@gmail.com <ab...@gmail.com> #44Dec 16, 2024 01:35PM

Add comment

Issue metadata