After the emulator update, the network speed is slow [243053479]

Verified

Bug

Status Update

No update yet.

Description

a7...@gmail.com

created issue #1

Aug 19, 2022 02:56PM

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.10-8807927
HAXM / KVM Version: gvm 65544.0.0

Android SDK Tools: 26.1.1

Host Operating System: Windows 10 Enterprise LTSC 2021

CPU Manufacturer: AMD CPU
Virtualization is supported
64-bit CPU

RAM: 32692 MB

GPU: GPU #1
Make: 1002
Model: Radeon (TM) RX 480 Graphics
Device ID: 67df

Build Fingerprint:

AVD Details: Name: Pixel_5_API_30
CPU/ABI: x86
Path: C:\Users\Tom\.android\avd\Pixel_5_API_30.avd
Target: google_apis [Google APIs] (API level 30)
Skin: pixel_4
SD Card: 512M
AvdId: Pixel_5_API_30
PlayStore.enabled: false
avd.ini.displayname: Pixel 5 API 30
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:3274126e0242a0d86339850416b0ce34
hw.device.manufacturer: Google

hw.device.name: pixel_5
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 440
hw.lcd.height: 2340
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-30\google_apis\x86\
runtime.network.latency: none
runtime.network.speed: full
showDeviceFrame: yes
skin.dynamic: yes
tag.display: Google APIs

tag.id: google_apis
vm.heapSize: 256

Steps to Reproduce Bug:network speed is too slow
Expected Behavior:

Observed Behavior:

Comments

ya...@google.com <ya...@google.com> Aug 19, 2022 05:06PM

Assigned to an...@google.com.

bo...@google.com <bo...@google.com> Aug 19, 2022 05:07PM

Reassigned to wd...@google.com.

r....@gmail.com <r....@gmail.com> #2Aug 20, 2022 04:37PM

There is no error when I use kotlin versions: 1.6.21, but issue/error starts appearing when kotlin version is 1.7.0

wd...@google.com <wd...@google.com> Aug 30, 2022 06:11PM

Accepted by wd...@google.com.

wd...@google.com <wd...@google.com> #3Aug 31, 2022 04:30PM

I have the same problem, i think no stable version of room 2.4.2 with kotlin 1.7.0

Message last modified on Aug 31, 2022 08:18PM

wd...@google.com <wd...@google.com> #4Aug 31, 2022 05:51PM

usage implementation 'androidx.room:room-ktx:2.5.0-alpha02'

Message last modified on Aug 31, 2022 06:06PM

wd...@google.com <wd...@google.com> #5Aug 31, 2022 06:21PM

me too

Message last modified on Aug 31, 2022 07:50PM

ra...@google.com <ra...@google.com> #6Aug 31, 2022 07:17PM

Thanks for the report I was able to reproduce the issue and indeed it occurs when using Kotlin 1.7.0. Sadly I don't have a workaround yet, but will investigate further.

wd...@google.com <wd...@google.com> #7Aug 31, 2022 07:35PM

and just to clarify, we see the issue when using Room 2.4.2, but not with Room 2.5.0-alpha02.

wd...@google.com <wd...@google.com> #8Aug 31, 2022 07:41PM

it occurs when kotlin version 1.7.0 and room 2.5.0-alpha02 as well to me. I solved the problem by downgrading kotlin version to 1.6.20

wd...@google.com <wd...@google.com> #9Aug 31, 2022 10:36PM

The same if you trying this Google-Developer Project:

https://github.com/google-developer-training/android-basics-kotlin-sql-basics-app
I updated everything - It wasn't running.
With ext.kotlin_version = "1.6.21" - it is running.

Message last modified on Sep 1, 2022 02:28PM

wd...@google.com <wd...@google.com> #10Sep 6, 2022 03:17PM

As a workaround, you can remove the "suspend" in the dao, but you need to explicitly specify the Dispatchers.IO when launching the coroutine.

wd...@google.com <wd...@google.com> Sep 9, 2022 08:17PM

Marked as fixed.

wd...@google.com <wd...@google.com> #11Sep 12, 2022 07:49PM

Hey all, looks like the issue is related to a change in Kotlin's @Metadata annotation and the way Room reads it, Room 2.4.2 is using an older version of the kotlinx-metadata-jvm library which does not support reading Kotlin 1.7 information, where as in Room 2.5.0 we updated the library.

To workaround this issue please force upgrade the dependency by adding it to your annotation processor path, i.e. add kapt "org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.5.0" if you are using Room 2.4.x.

Meanwhile, I'll work on releasing a Room 2.4.3 that is compatible with Kotlin 1.7 since Room 2.5.x is still in development.

Message last modified on Sep 12, 2022 07:49PM

ra...@google.com <ra...@google.com> #12Sep 12, 2022 08:47PM

Thanks a lot. Now its working good for me.

ra...@google.com <ra...@google.com> #13Sep 13, 2022 09:51PM

Verified by ra...@google.com.

Thanks! Do you think 2.4.3 is something that will be released in the next couple weeks? Trying to decide if I want to use the workaround or just wait until it is released.

jb...@gmail.com <jb...@gmail.com> #14Oct 15, 2022 01:45PM

We have an upcoming androidx release in July 20, I am trying to aim for that.

I also wanted to mention that if you migrate to using KSP instead of KAPT you won't run into this issue, as long as you use the KSP version that is compatible with Kotlin 1.7.0 which is 1.7.0-1.0.6.