access to mSelectorPosition and mSelectorRect will be removed by the Android Framework #497
Comments
SlimShadys
pushed a commit
to Aospify/platform_frameworks_base
that referenced
this issue
Sep 9, 2020
These two fields were accessed via reflection by certain apps but they are not really designed to be public API. Moreover, these usages seem to come from an open source project and I've created an issue there to notify the owners. emilsjolander/StickyListHeaders#497 Bug: 123768403 Bug: 123769365 Test: existing tests pass Change-Id: I7d6beba8ea7e9b9a406ea2332bcccfd283db8196
|
Hi @yigit , Have you solved it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
This library is accessing 2 private APIs from
AbsListViewin WrapperViewList.Apps targeting API Q+ will not be able to access those fields via reflection anymore. These fields are not designed to be changed outside the class and is likely to cause problems.
We recommend using RecyclerView going forward which provides necessary APIs to implement sticky headers. As far as I can see, the code seems to handle not being able to access these fields properly but just wanted to give a heads up.
The text was updated successfully, but these errors were encountered: