-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Rethink 0 day support for new android versions #86
Comments
The correct way of getting the android version is
Metadata handlingThe current implementation uses only metadata for single android.jar version. This is problematic since the application can run on older versions that have the same public API, but with different non public class hierarchy. The prototype representation at runtime requires the correct class hierarchy even if it is not public. Possible way of handling this
|
After a short discussion we think we might be able to fix the metadata handling by compensating for class hierarchy changes. This will not require any metadata merging and diff-ing. Still in the future we might need this. |
Currently minSDKVersion is referred to when building. This is not correct. We need new way to handle how and from where we reference android.jar on build.
This will also require redesigning how we handle metadata versions across different devices and different android versions at run time.
The text was updated successfully, but these errors were encountered: