Fixed
Status Update
Comments
db...@gmail.com <db...@gmail.com> #2
Duplicate of internal issue
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 45a1bc4a15b5b10d0635d79fb55df2aced5a2a4a
Author: Alan Viverette <alanv@google.com>
Date: Thu May 14 18:06:25 2020
Only apply DayNight changes to Activity-hosted delegates
Dialogs can't receive configuration change callbacks, so there's no point
in updating their configurations. They'll have to be destroyed and re-
created by their host activities. Also, dialogs were eating the changes.
Fixes: 155379937
Test: NightModeForegroundDialogTestCase and appcompat test suite
Change-Id: Ifa18d9d42268ec8821223942dc6c817ecabbed7f
A appcompat/appcompat/src/androidTest/java/androidx/appcompat/app/NightModeDialogFragment.java
A appcompat/appcompat/src/androidTest/java/androidx/appcompat/app/NightModeForegroundDialogTestCase.kt
M appcompat/appcompat/src/main/java/androidx/appcompat/app/AppCompatDelegate.java
M appcompat/appcompat/src/main/java/androidx/appcompat/app/AppCompatDelegateImpl.java
vi...@google.com <vi...@google.com>
bo...@google.com <bo...@google.com>
wd...@google.com <wd...@google.com> #3
I think, sActiveDelegates
meant "live" delegates. Anyway, now there's a mess :(
private static final ArraySet<WeakReference<AppCompatDelegate>> sActivityDelegates;
private static final Object sActivityDelegatesLock;
static void addActiveDelegate(@NonNull AppCompatDelegate delegate);
static void removeActivityDelegate(@NonNull AppCompatDelegate delegate);
private static void removeDelegateFromActives(@NonNull AppCompatDelegate toRemove);
private static void applyDayNightToActiveDelegates();
Source:
wd...@google.com <wd...@google.com>
wd...@google.com <wd...@google.com> #5
Rc02 is work for me, thanks for your work!
wd...@google.com <wd...@google.com>
db...@gmail.com <db...@gmail.com> #6
It is not fixed. The problem is still there exactly as it was, with all Android Studio updates and old and new emulated devices.
Was it not yet published?
Was it not yet published?
wd...@google.com <wd...@google.com> #7
Could you share with me the emulator version? Would it be possible to try the latest emulator canary release?
wd...@google.com <wd...@google.com> #8
It turns out the fix is not cherry-picked into
[Deleted User] <[Deleted User]> #9
d6:76:5f:6f:23:8b
Description
Please Read:https://developer.android.com/studio/report-bugs.html#emulator-bugs
Android Studio Version: Unknown
Emulator Version (Emulator--> Extended Controls--> Emulator Version): 31.3.14-9322596 HAXM / KVM Version: HAXM 7.6.5
Android SDK Tools: 26.1.1
Host Operating System: Windows 10 Pro
CPU Manufacturer: Intel CPU Virtualization is supported 64-bit CPU
RAM: 16327 MB
GPU: GPU #1 Make: 1002 Model: AMD Radeon HD 7570 Device ID: 675d
Build Fingerprint:
AVD Details: Name: Pixel_2_API_33_2 CPU/ABI: x86_64 Path: C:\Users\Doron.android\avd\Pixel_2_API_33_2.avd Target: google_apis_playstore [Google Play] (API level 33) Skin: pixel_2 SD Card: 512M AvdId: Pixel_2_API_33_2 PlayStore.enabled: true avd.ini.displayname: Pixel 2 API 33 2 avd.ini.encoding: UTF-8 disk.dataPartition.size: 6442450944 fastboot.chosenSnapshotFile: fastboot.forceChosenSnapshotBoot: no fastboot.forceColdBoot: no fastboot.forceFastBoot: yes hw.accelerometer: yes hw.arc: false hw.audioInput: yes hw.battery: yes hw.camera.back: virtualscene hw.camera.front: emulated hw.cpu.ncore: 4 hw.dPad: no hw.device.hash2: MD5:55acbc835978f326788ed66a5cd4c9a7 hw.device.manufacturer: Google hw.device.name: pixel_2 hw.gps: yes hw.gpu.enabled: yes hw.gpu.mode: auto hw.initialOrientation: Portrait hw.keyboard: yes hw.lcd.density: 420 hw.lcd.height: 1920 hw.lcd.width: 1080 hw.mainKeys: no hw.ramSize: 1536 hw.sdCard: yes hw.sensors.orientation: yes hw.sensors.proximity: yes hw.trackBall: no image.sysdir.1: system-images\android-33\google_apis_playstore\x86_64
runtime.network.latency: none runtime.network.speed: full showDeviceFrame: yes skin.dynamic: yes tag.display: Google Play tag.id: google_apis_playstore vm.heapSize: 228
Steps to Reproduce Bug:
Write Hebrew characters when sending a message - the message is not sent. Same happens if sent programmatically from another app. The happens on API 33 but not on API 29.
Expected Behavior:
Observed Behavior: