-
Notifications
You must be signed in to change notification settings - Fork 374
Is ReLinker still required after API 21? #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
See #64. The tl;dr is that we don't actually know at which API level relinker is no longer needed. To find out would require either a) learning way more about AOSP or b) removing relinker and seeing who crashed. Neither of those seems likely to happen any time soon. Rumor has it that it's safe to load libraries without relinker as of API 23, but I'd strongly advise you to verify that for yourself. |
The library search order issues were fixed with JB MR2 (API 18) iirc. The issue remains for I don't remember when the installer issues were fixed, but API 23 is roughly the right era. @enh-google might remember better. |
correct. see https://android.googlesource.com/platform/bionic/+/master/android-changes-for-ndk-developers.md#changes-to-library-dependency-resolution for details (where we ever suggest that anyone hit by this should use ReLinker :-) ).
sadly not, and -- whenever it was -- it was long enough ago that i couldn't find the bug. but, yeah, that feels like the right era. iirc the package manager folks thought they'd fixed it in 21 (and did at least improve things there), but there were some lingering issues for a while longer. |
Thanks for the authoritative answers! I'll open a documentation PR and just call it at API 24 to be safe. |
The
ReLinker.java
javadoc says:But I can't find any official documentation on the Relinker blog [1][2] or in the readme saying the last Android version where Relinker is still required. Could you please add some documentation about this?
The text was updated successfully, but these errors were encountered: