Status Update
Comments
an...@google.com <an...@google.com> #2
Please help us out! If you are planning to work on this issue within the next year, please reply indicating the timeline you intend to complete the work and remove the "Android Blintz Close Candidate" hotlist. If it is expected for this issue to take multiple years to resolve, please add it to the android_icebox hotlist (
Stale issues that aren't removed from the "Android Blintz Close Candidate" will be closed in 7 days, so if you think this should be closed there's no need to do anything. For more information please see go/android-blintz.
If you are not the assignee of this bug, and feel this issue needs to be escalated, please email the components default assignee with the bug number, and what you'd like to escalate.
an...@google.com <an...@google.com> #3
For more information please see go/android-blintz.
ja...@google.com <ja...@google.com>
an...@google.com <an...@google.com> #4
For more information please see go/android-blintz.
ja...@google.com <ja...@google.com>
ni...@google.com <ni...@google.com>
ni...@google.com <ni...@google.com> #5
Tagging with a review tag so that Jetpad picks it up
[LIBRARY_API_REVIEW_TAG:core/core/api/1.4.0-alpha01.txt]
al...@google.com <al...@google.com> #7
Oh, okay -- it's a feature request to add that method.
ki...@google.com <ki...@google.com> #8
Handler.hasCallbacks was added in JB timeframe in
It was marked as @hide, so technically we can use reflection on pre-29 versions to get to it. But what would we do ICS? Nothing?
ki...@google.com <ki...@google.com> #9
And on ICS there is no underlying MessageQueue API to check for runnable callbacks. That was added as part of the same original CL at
Note that we didn't see a single internal or external request to actually expose this API in AndroidX in a backwards compatible way.
al...@google.com <al...@google.com> #10
It would have to be RequiresApi(JELLY_BEAN)
, but if the @hide
method was on the non-SDK-usage blacklist in P then we're out of luck.
ki...@google.com <ki...@google.com> #11
Where do I find that blacklist?
al...@google.com <al...@google.com> #12
You could either check the status manually by searching in a CSV (SDK 29) and TXT (SDK 28):
Or go ahead and write it and then pass the library through veridex
:
ki...@google.com <ki...@google.com>
al...@google.com <al...@google.com> #13
It's light-greylist on SDK 28, so we should be able to reflect on SDK 16+.
al...@google.com <al...@google.com> #14
Though if an OEM changed the implementation, we're going to have to throw an exception. It's unlikely, but it's there.
al...@google.com <al...@google.com> #15
Still waiting on core
to go back to alpha... This is waiting in aosp/1580773.
ap...@google.com <ap...@google.com> #16
Branch: androidx-main
commit 7e9c4bfcbd0a3bebc25ec4747922bcf80cd278fe
Author: Alan Viverette <alanv@google.com>
Date: Mon Feb 08 17:41:41 2021
Add compat method for Handler.hasCallbacks()
Fixes UnsafeNewApiCall errors, fixes APIs that were incorrectly targeting
API 16, improves exception logging. Cleans up test formatting.
Relnote: "Adds Handler.hasCallbacks() method for parity with platform SDK"
Fixes: 113855676
Test: HandlerCompatTest#testHasCallbacks, HandlerCompatTest
Change-Id: Idce1c9fbe0d93bd9ebcb26716a63834bb1c4c12d
M core/core/api/current.txt
M core/core/api/public_plus_experimental_current.txt
M core/core/api/restricted_current.txt
M core/core/src/androidTest/java/androidx/core/os/HandlerCompatTest.java
M core/core/src/main/java/androidx/core/os/HandlerCompat.java
Description
--
Please add.