Skip to content
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

Correct Attribute Resolution #3123

Merged
merged 5 commits into from
Jul 4, 2023
Merged

Correct Attribute Resolution #3123

merged 5 commits into from
Jul 4, 2023

Commits on Jul 3, 2023

  1. Configuration menu
    Copy the full SHA
    0eca0c8 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    0488d4b View commit details
    Browse the repository at this point in the history

Commits on Jul 4, 2023

  1. Configuration menu
    Copy the full SHA
    e2d0d37 View commit details
    Browse the repository at this point in the history
  2. fix: reverse order of processing to trust string pool 2nd

    Android prefers the resource map value over what the String block has.
    This can be seen quite often in obfuscated apps where values such as:
     <item android:state_enabled="true" app:state_collapsed="false" app:state_collapsible="true">
    Are improperly decoded when trusting the String block.
    Leveraging the resource map allows us to get the proper value.
     <item android:state_enabled="true" app:d2="false" app:d3="true">
    iBotPeaches committed Jul 4, 2023
    Configuration menu
    Copy the full SHA
    21d07bb View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    7a35f7f View commit details
    Browse the repository at this point in the history