IssueTracker

Good news! Wear Compose has been updated to ab/13046075 in https://critique.corp.google.com/cl/732905175 and this bug has been affected.

Ok fine, after clicking on each button, we see the issue right. button clicks are not observable from the video you have attached.

BTW, We have passed this defect on to the development team and will update this issue with more information as it becomes available.

Thanks

Hi,
The development team has fixed the issue that you have reported and it will be available in a future build
Thanks

Hi, Could you please let us know whether it is an issue from AppCompat or it is an issue from the sample code of AppCompat? And based on the fact that this issue could be reproduced easily on any device target 23, it undermines my confidence in the quality of code in AppCompat. How could it pass the test at the very beginning?

It's issue with AppCompatActivity.java of support library which is fixed now.

[Comment deleted]

Issue is not fully fixed. I'm using "values-night" plus normal "values"
directories as well as
android:configChanges="orientation|screenSize".
But when performing orientation change, the colors inside "values-night"
get confused with "values" colors for some components like recyclerview
items and newly created fragments. I will upload a sample project that
reproduces the issue.
Στις 11 Μαρ 2016 2:42 πμ, ο χρήστης <android@googlecode.com> έγραψε:

I'm also still having some of the wrong resources being used. Additionally, the Support7Demo's AlertDialog demo still doesn't work, the dialogs are all light. The Dialog (not AlertDialog) demo does work.

 Nexus 6P 6.0.1 and Galaxy S5 5.0

I modified the cheesesquare project to let you know what I mean.

App starts on night mode explicitly. While on night mode, rotate your phone to landscape scroll a little bit then rotate to portrait scroll again. A glitch appears where resources from default "values" (light theme) are being used instead.

check it out here
https://github.com/ThanosFisherman/cheesesquare

Re: #13
I think something along the lines of the following snippet will work around the specific issue you're having. This worked for me, though I suspect it needs more fleshing out to handle auto night mode and to handle N's system toggle.

    @Override
    public void onConfigurationChanged(Configuration newConfig) {
        int currentNightMode = getResources().getConfiguration().uiMode
                & Configuration.UI_MODE_NIGHT_MASK;

        if (currentNightMode == Configuration.UI_MODE_NIGHT_YES)
          newConfig.uiMode = (newConfig.uiMode & ~Configuration.UI_MODE_NIGHT_MASK) | Configuration.UI_MODE_NIGHT_YES;

        super.onConfigurationChanged(newConfig);
       
    }



I'm having issues with mixed resources but am not handling configuration changes. I haven't been able to make a test case yet. In my setup first time viewing the activity in either or dark works and then toggling once works, but toggling back to the original state keeps some elements of the other, like the list dividers and vector drawables that were tinted to ?attr/colorControlActivated. My setup does work if I just switch between using a light and dark theme, it's the -night values that throws things off. I'm not concerned that what appcompat daynight is trying to do can be done reliably and I'll need my dark theme independent of -night, and -night just to handle N.

[Comment deleted]

[Comment deleted]

[Comment deleted]

Same issue is not fixed, we are seeing it within our app. When we come through a deep link with night mode enabled, scrolling down through a recyclerview shows some view holders as applying non -night values.

Can confirm issue is not fixed with support library 25.1.0

Can confirm issue is not fixed with support library 26.0.0

confirm issue is not fixed with support library 25.4.0

Also having problems with wrong resources using 26.0.0
Rotating from landscape -> portrait -> landscape works fine however going from landscape (left) -> landscape (right) messes up the resources. Most of the existing UI looks fine but all new views receives the wrong resources.

confirm issue is not fixed with support library 25.0.0 .

Now, i got this bug in android 8.1, after rotate phone, some new widget got error resource.

This issue definitely isn't fixed yet, getting it starting with Android 5.0. I found the easiest way to reproduce it 100% is to implement Lokalise SDK here https://github.com/lokalise/lokalise-android-sdk and then -night colors won't be used for new views (RecyclerView items, dialog views, etc.) as soon as onStop() is called, e.g. after going to another activity and coming back or putting the app to background and bringing it back to front. Please fix this!

After 3 years this is still not fixed. The theme -night colors works when an app first starts, but then any subsequent starts from the desktop reverts colors back to non-night ones. As indicated, it looks like any onStop() will mess future starts of an application.

Try calling the delegator method on the very first screen your app opens. I was having the same problem and it is starts working once I move the delegator code to the very first screen i.e. Splash Screen.