WAI
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Can you confirm if this is a regression compared to a previous version you were using?
[Deleted User] <[Deleted User]> #3
Please provide info on the device model and API level used to reproduce the bug.
Running the sample above (with surface) at tip of tree on a pixel 7 device, I am able to observe the text change and button's ripple effect.
do...@gmail.com <do...@gmail.com> #4
I have attached a reproducer project. I think the key point is to also wrap RootContent
with Surface {}
.
class MainActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
enableEdgeToEdge()
setContent {
Surface {
RootContent()
}
}
}
}
vi...@google.com <vi...@google.com>
es...@google.com <es...@google.com>
[Deleted User] <[Deleted User]> #5
Reproducible on an API 34 emulator.
Properties
avd.ini.displayname Pixel 7 API 34
avd.ini.encoding UTF-8
AvdId Pixel_7_API_34
disk.dataPartition.size 6442450944
fastboot.chosenSnapshotFile
fastboot.forceChosenSnapshotBoot no
fastboot.forceColdBoot yes
fastboot.forceFastBoot no
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.device.hash2 MD5:3db3250dab5d0d93b29353040181c7e9
hw.device.manufacturer Google
hw.device.name pixel_7
hw.dPad no
hw.gps yes
hw.gpu.enabled yes
hw.gpu.mode auto
hw.initialOrientation Portrait
hw.keyboard yes
hw.lcd.density 420
hw.lcd.height 2400
hw.lcd.width 1080
hw.mainKeys no
hw.ramSize 2048
hw.sdCard yes
hw.sensors.orientation yes
hw.sensors.proximity yes
hw.trackBall no
image.androidVersion.api 34
image.sysdir.1 system-images/android-34/google_apis_playstore/arm64-v8a/
PlayStore.enabled true
runtime.network.latency none
runtime.network.speed full
showDeviceFrame yes
skin.dynamic yes
tag.display Google Play
tag.id google_apis_playstore
tag.ids google_apis_playstore
vm.heapSize 228
rp...@google.com <rp...@google.com> #6
It's also reproducible with Compose 1.8.0-alpha05
and M3 1.2.0
. Not reproducible with Compose 1.8.0-alpha04
and M3 1.2.0
. Looks like the regression was introduced in Compose 1.8.0-alpha05
.
Description
I've installed the latest Android studio and want to create emulator but cannot in case error hapens
" Unable to run mksdcard.exe SDK tool."
There are many information about this problem for Ubuntu for example, but I can't find any information how to fix it on windows
Environment options
Build: AI-191.8026.42.35.5900203, 201909252113,
AI-191.8026.42.35.5900203, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080
AS: 3.5.1; Android Gradle Plugin: 3.2.1; Gradle: 5.4.1; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
=== About ===
Build version: Android Studio 3.5.1 Build #AI-191.8026.42.35.5900203 September 26, 2019
Java version: 1.8.0_202-release-1483-b03amd64
Operating System: Windows 10 (10.0, amd64)
JVM version: OpenJDK 64-Bit Server VM JetBrains s.r.o
=== System ===
Number of CPU: 8
Used memory: 442Mb
Free memory: 255Mb
Total memory: 698Mb
Maximum available memory: 1237Mb
=== Displays ===
Displays:
Display 0: 1920x1080; scale: 1,00
=== Plugins ===
Custom plugins: [Darkyen's Time Tracker (1.4.3)]
Disabled plugins:[]