Fixed
Status Update
Comments
as...@google.com <as...@google.com>
it...@gmail.com <it...@gmail.com> #3
I think that ResultReceiver will "forever" stay in the old package since otherwise it would be a breaking AIDL-related change.
ca...@google.com <ca...@google.com> #4
Yep, it has to stay in the old package.
> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"
Config issue.
> Jetifier is changing the import in the library to "androidx.core.os.ResultReceiver"
Config issue.
it...@gmail.com <it...@gmail.com> #5
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
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:
Bug:
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
ca...@google.com <ca...@google.com>
ap...@google.com <ap...@google.com> #6
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 .
Description
androidx.core:core-splashscreen
1.0.0-beta01
Theme.SplashScreen
False
Pixel 4a (5G) (Android 11)
A small number of users are affected by this crash (report via
Crahlytics
) & it seems to be very device-specific (mentioned above).Stacktrace:
The
handleSeamlessEnd
extension method: