Feature Request P1
Status Update
Comments
h6...@gmail.com <h6...@gmail.com> #2
доколе?
to...@gmail.com <to...@gmail.com> #3
+1
There should be possible to open source in any installed (or minSdk for project) android API version, because compileSdk is not only one used for run the app.
Why it takes so long to release source code to SDK when the sources was already pushed to GIT?
There should be possible to open source in any installed (or minSdk for project) android API version, because compileSdk is not only one used for run the app.
Why it takes so long to release source code to SDK when the sources was already pushed to GIT?
[Deleted User] <[Deleted User]> #4
Fuck this issue, always happened from android 23. Fuck this. Not friendly to developers
zo...@gmail.com <zo...@gmail.com> #6
yep, no 26 sources no funny ;(
all the bunnies gonna cry ;((
all the bunnies gonna cry ;((
zo...@gmail.com <zo...@gmail.com> #7
nk...@gmail.com <nk...@gmail.com> #8
+1
rp...@google.com <rp...@google.com>
ad...@google.com <ad...@google.com> #9
While debugging, we consider this behavior WAI. That's because stepping through code that doesn't match SDK version of the device is not a good experience. However, we can consider fallbacks to older sources when navigating to definitions while editing your code.
Description
Allowing fallback to at least see older sources directly from studio and switch to sources I already have downloaded would be a massive help.
Android Studio 2.3 Canary
Build #AI-162.3454121, built on November 8, 2016
JRE: 1.8.0_112-release-b05 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o