Ilya Polenov
Ilya Polenov
I think the change responsible for this issue is this one or something related to it: https://android.googlesource.com/platform/tools/base/+/acf0ab389c444a85371b897d8b2c81d96d31b988 Maybe it'll help figuring out how to workaround this
I have managed to sync with android gradle plugin 3.2.1, 3.3 RC and 3.4 alpha with android.jar assembled from .class files built from AOSP sources. When adding any .class from...
Of course it won't help with the issue of blacklisted APIs with [the new Google policy](https://developer.android.com/about/versions/pie/restrictions-non-sdk-interfaces).
Here's [android.jar](https://github.com/anggrayudi/android-hidden-api/files/2709802/android.zip) for API level 28, which I use.
@mleeaura I've assembled it from AOSP sources. Seems like pulling framework from device no longer works.
Sorry, kind of busy lately and I don't have the environment to repeat the process right now. When Android Q is released I'll probably do it again. Basically I just...
Something like that. As I remember, I also used MockableJarGenerator from the post above to determine which classes fail the transform. I could have removed some of those.
I tried to reproduce the same steps I did last time with P for Q preview 5, but failed. So I had to improvise and generated android.jar from original android.jar...
Oh yeah, it doesn't have internal resources because I don't need them
Seems like this is still an issue in 2.0.0-alpha snapshot version