Status Update
No update yet.
Comments
uc...@google.com
We use build flavours heavily with a lot of common code. The refactoring support in AS is really good but it continually catches us out when it doesn't work across all flavours in a project. It's a big gap for serious product development.
[Deleted User] <[Deleted User]>
We at my company need this same feature. We have a lot of white labels and need refactor the same class across flavours. :(
[Deleted User] <[Deleted User]>
+1, I need this very badly
xa...@google.com
an...@google.com
+1 My company also need this feature.
[Deleted User] <[Deleted User]>
Can we atleast know the status of the issue please? Will it be fixed or is it in low priority. It's been 4 years.
an...@google.com
We are currently investigating possibly solutions.
xa...@google.com
[Deleted User] <[Deleted User]>
+1 This will exclude a lot of unnecessary work. In my work I have 25 flavours. :(
an...@google.com
+1 .. we need it as well...
Description
Build #AI-145.3537739, built on December 2, 2016
JRE: 1.8.0_112-release-b05 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
OS: Mac OSX 10.12
Version of Gradle Plugin: 2.2.3
Version of Gradle: 2.14.1
externalNativeBuild with ndkBuild
Steps to Reproduce:
- I used project from here:
- Set the breakpoint anywhere in while loop in main.cpp
- choose Run -> Debug 'app'
- app launches, breakpoint isn't being hit, there is a "Starting LLDB server" text in status bar, which never changes
- add a breakpoint in SampleActivity.java, i.e. in onStart() or in onBackPressed()
- make an app hit that new java breakpoint (though app doesn't go into a debug session at that moment, doesn't suspend)
- immediately LLDB debugger attaches and C++ breakpoint is being hit, debug session starts normally (for the C++ breakpoint)
same behaviour with a different, big project, I'm working on