You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I found that the compiler sometimes generates bridge and synthetic methods See link for more info, some of them have the same name than the original one and the last used conditionals weren't good enough identifying these two different methods. The I_ACCESS_LIST allows the differentiation among them
Example:
Original method:
I_ACCESS_LIST values for this method: public
bridge and synthetic compiler generated method:
I_ACCESS_LIST values for this method: public bridge synthetic
With this change the tool is able to differentiate and instrument the right method without generating problems in the smali files.
This new change is highly related to the issue #8 it may start decreasing the list mentioned in that issue
The text was updated successfully, but these errors were encountered:
Recently I found that the compiler sometimes generates bridge and synthetic methods See link for more info, some of them have the same name than the original one and the last used conditionals weren't good enough identifying these two different methods. The I_ACCESS_LIST allows the differentiation among them
Example:
I_ACCESS_LIST values for this method: public
I_ACCESS_LIST values for this method: public bridge synthetic
With this change the tool is able to differentiate and instrument the right method without generating problems in the smali files.
This new change is highly related to the issue #8 it may start decreasing the list mentioned in that issue
The text was updated successfully, but these errors were encountered: