Incorrect ResultReceiver mapping - Jetifier [123651524]

Fixed

Bug

[AOSP] assigned

Status Update

No update yet.

Description

ga...@gmail.com

created issue #1

Jan 31, 2019 11:35AM

I am using a third party dependency (provided as an aar) which makes use of ResultReceiver from the Support-v4 library (android.support.v4.os.ResultReceiver). After migrating my app to AndroidX, Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver" which is causing a ClassNotFoundException during runtime because ResultReceiver has not yet been moved to the new AndroidX package.

Exception:
Caused by: java.lang.ClassNotFoundException: Didn't find class "androidx.core.os.ResultReceiver"

ResultReceiver in AndroidX Core, it is still in package android/support/v4/os:

https://android.googlesource.com/platform/frameworks/support/+/androidx-master-dev/core/src/main/java/android/support/v4/os

Sample project:

https://github.com/hibob224/jetifier-test

Android Studio:
Android Studio 3.3
Build #AI-182.5107.16.33.5199772, built on December 25, 2018
JRE: 1.8.0_152-release-1248-b01 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.13.6

Comments

ad...@google.com <ad...@google.com> #2Jan 31, 2019 11:57AM

Assigned to ki...@google.com.

ki...@google.com <ki...@google.com> #3Feb 11, 2019 09:59PM

Reassigned to pa...@google.com.

lblb636@ Thanks for reporting this bug. I just want to confirm that the issue is the call device button being not responsive according to the uploaded video. It seems like this issue only happened on Windows.

al...@google.com <al...@google.com> #4Feb 11, 2019 10:11PM

@3 Why does it occur?
And why only from specific API of Android?
On API 28 for example, it doesn't occur...

Please fix this issue for all API versions of the emulator.

ap...@google.com <ap...@google.com> #5Feb 13, 2019 02:04PM

Another similar issue that's related https://b.corp.google.com/issues/226426377

hu...@google.com <hu...@google.com> #6Apr 1, 2019 04:39PM

RE#4 I need to try this on Windows laptop first and I couldn't repro on MacOS or Linux. But I think this is most likely related to the modem simulator we introduced for API 31. Will need to further investigate.

pa...@google.com <pa...@google.com> #7Oct 25, 2019 01:12PM

Marked as fixed.

@6 There are plenty of issues on emulator API 31 (and on Android 13 emulator). Many glitches. Spend 5 minutes on it and you will notice.
Why isn't the emulator tested more on Windows OS?
Windows OS is more popular than Linux and MacOS combined (on desktop) ...

Issue 123651524