Assigned
Status Update
Comments
ch...@google.com <ch...@google.com> #2
I just attached a minimal test application with duplicated and multiline traces. Provided are a couple of logcat files and screenshots.
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
To me this isn'r really a big problem, since AS compiles my application and lets me debug it. That's what I use it for in my company. I just found it a bit annoying that something that worked one way in AS 2.x and 3.0, suddenly changed in 3.1. The new way results more time-consuming to me while debugging and reviewing the logs.
Could this be made configurable? Not necessarily in the UI, but editing some properties file. Thanks. :)
is...@revolut.com <is...@revolut.com> #3
I have the same problem.
ch...@google.com <ch...@google.com> #4
I also have the same problem.
is...@revolut.com <is...@revolut.com> #5
I also have the same problem.
sg...@google.com <sg...@google.com> #6
I also have the same problem.
Description
We are developing an SDK and want to obfuscate it with
minifyEnabled=true
.However, when an application is launched with the obfuscated SDK, it crashes with the following error:
To simplify the issue, we have provided BugExample.zip in attachments, which contains a minimal reproducible example.
:app
and:mylibrary
.:mylibrary
is an SDK that we want to obfuscate;:app
is demo application that integrates this SDK;:mylibrary
module, we have two classes:NavBarScrollingBehaviour
andNavBarUsage
;NavBarScrollingBehaviour
extendsAppBarLayout.ScrollingViewBehavior
which itself extendsHeaderScrollingViewBehavior
;HeaderScrollingViewBehavior
has two final methodssetOverlayTop
andgetOverlayTop
;NavBarUsage
class these two methods are used;:mylibrary
, the generated mapping.txt file contains two suspicious lines:Looks like R8 adds these two synthetic methods during obfuscation and optimization which conflict with the original final methods from
HeaderScrollingViewBehavior
.If we slightly modify
NavBarScrollingBehaviour
code as follows, the crash disappears:Is there a way to prevent R8 from adding these synthetic methods during obfuscation adn optimization?