IssueTracker

Issue is reproducible. More details are here : https://drive.google.com/corp/drive/folders/1VwmAs_ixSYXoxYzcfwoHqyJ2f9w4DzZq  (internal only link).

I think that ResultReceiver will "forever" stay in the old package since otherwise it would be a breaking AIDL-related change.

Yep, it has to stay in the old package.

> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"

Config issue.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19
Author: Filip Pavlis <pavlis@google.com>
Date:   Tue Feb 12 19:41:53 2019

    Revert changes in default.config and remove task.
   
    It turned out that we have released (as part of beta03) mappings that
    were not supposed to be used externally. This is because we were actively
    maintaining "dejetifyArchive" task without realizing that next jetifier
    update will contain such changes. As we are done with 28.0.0 I think it
    is a good time to sunset the "dejetifyArchive" target. I also reverted
    all the config changes that are not supposed to go outside. Please note
    that there is still "partiallyDejetifyArchive" for migration purpouses
    and is still part of continuous build.
   
    Also added ignore rule for ResultReceiver.
   
    Bug: b/123651524
    Bug: b/124291947
    Test: N/A
    Change-Id: I59983d25ae7e0939f2e9e54005460ad0f73beb3c

M       buildSrc/jetify.gradle
M       buildSrc/src/main/kotlin/androidx/build/AndroidXPlugin.kt
M       buildSrc/src/main/kotlin/androidx/build/LibraryVersions.kt
M       jetifier/jetifier/core/src/main/resources/default.config
M       jetifier/jetifier/core/src/main/resources/default.generated.config

https://android-review.googlesource.com/902433
https://goto.google.com/android-sha1/2bf39653103b1ce6b3b6fc64b44faaa9fcad1c19

FYI, in AGP 3.4.0-rc03 and 3.5.0-alpha09, the AGP has been updated to use Jetifier 1.0.0-beta04, which should have the fix for the above issue: https://android.googlesource.com/platform/tools/base/+/f7fdfbb94aebb43b7e9515c683fd71b8c905ee79.

Closing as fixed.

Yep, Jetifier will automatically convert ProGuard rules packaged with libraries, but if you're adding the ProGuard files to your own project, you'll need to make sure to use the AndroidX equivalents if your project is using AndroidX.

This issue seems to be back again? ... I'm using v2.2.0-rc02 and have run into the issue. Using the proguard rule below (mentioned  in #7 above) to work around the issue seems to fix it.

-keepclassmembers class androidx.appcompat.graphics.drawable.DrawerArrowDrawable {
    void setProgress(float);
}

Looking at the commit linked above that fixed the issue originally, it adds a proguard rule to fix the issue for the old support library, but not a rule for the AndroidX equivalent. #8 suggests that Jetifier will handle the AndroidX conversion, but that doesn't seem to be the case? I'm using AndroidX and Jetifier and without the specfic -keep rule above for androidx, my back arrow icon gets removed in release (minified) builds.

Re #11, I do have jetifier enabled, and still see the regression mentioned in #9