Status Update
No update yet.
Comments
uc...@google.com
je...@google.com
pa...@gmail.com
Attached about beta. It constantly telling me it will update gradle plugin, but it seems it already have.
Android Studio 4.1 RC 1
Build #AI-201.8743.12.41.6719854, built on July 29, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1970M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation, org.intellij.plugins.markdown, org.jetbrains.kotlin
Android Studio 4.1 RC 1
Build #AI-201.8743.12.41.6719854, built on July 29, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1970M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation, org.intellij.plugins.markdown, org.jetbrains.kotlin
hu...@google.com
And same for canary.
Also attached the project.
Also attached the project.
si...@gmail.com
Thanks for the report. To let you know about progress on this:
- the project won't open on 4.0, as it uses AGP 4.1 features, which Studio 4.0 doesn't support;
- the PlayCoreKtx project has been updated so that it should open without trouble on 4.1 RC1;
- the issue with Studio looping over upgrading the plugin version is a real one, so it won't open on current canaries, which automatically attempt (and fail) to upgrade the project. I'm expecting that we will fix this before 4.2 Beta.
Thanks again!
hu...@google.com
@4 Please always make sure your projects work, and write which Android Studio versions are supported or not.
I've tried now again with the currently latest versions of each.
This time, the canary and the stable failed, but the beta didn't.
See attached.
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 25, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 7954M
Cores: 12
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins: String Manipulation, org.jetbrains.kotlin, com.google.services.firebase, ignaciotcrespo.github.com.vector-drawable-thumbnails, org.intellij.plugins.markdown
Android Studio 4.1 RC 1
Build #AI-201.8743.12.41.6719854, built on July 29, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1970M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation, org.intellij.plugins.markdown, org.jetbrains.kotlin
Android Studio 4.2 Canary 8
Build #AI-202.6397.94.42.6787931, built on August 25, 2020
Runtime version: 11.0.7+10-b765.53 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2038M
Cores: 12
Registry: ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation
I've tried now again with the currently latest versions of each.
This time, the canary and the stable failed, but the beta didn't.
See attached.
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 25, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 7954M
Cores: 12
Registry: ide.new.welcome.screen.force=true
Non-Bundled Plugins: String Manipulation, org.jetbrains.kotlin, com.google.services.firebase, ignaciotcrespo.github.com.vector-drawable-thumbnails, org.intellij.plugins.markdown
Android Studio 4.1 RC 1
Build #AI-201.8743.12.41.6719854, built on July 29, 2020
Runtime version: 1.8.0_242-release-1644-b01 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 1970M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation, org.intellij.plugins.markdown, org.jetbrains.kotlin
Android Studio 4.2 Canary 8
Build #AI-202.6397.94.42.6787931, built on August 25, 2020
Runtime version: 11.0.7+10-b765.53 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 2038M
Cores: 12
Registry: ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: String Manipulation
Description
Android Plugin Version: 3.0.1
Module Compile Sdk Version: 27
Module Build Tools Version: plugin default
Android SDK Tools version: 26.1.1
In the attached project you can run `gradlew assembleDebugAndroidTest --console=plain` and it'll run ProGuard on the test APK.
producing `build\outputs\apk\androidTest\debug\android-gradle-library-shrink-debug-androidTest.apk`
minifyEnabled false 1.2M APK (3.5M classes)
minifyEnabled true 1.1M APK (2.7M classes)
Notice that gradle task `transformClassesAndResourcesWithProguardForDebugAndroidTest` ran (easy, as it logs a lot).
Now, go into the build.gradle file and change `com.android.application` to `com.android.library` or `com.android.feature`.
It produces the same APK file as before, but ProGuard is not executed:
minifyEnabled false 1.2M APK (3.5M classes)
minifyEnabled true 1.2M APK (3.5M classes)
in fact, these two APKs are binary-equal.
For confirmation I tried `com.android.library` + `minifyEnabled true` + `gradlew transformClassesAndResourcesWithProguardForDebugAndroidTest`
and the result is:
Task 'transformClassesAndResourcesWithProguardForDebugAndroidTest' not found in root project 'android-gradle-library-shrink'.
This issue came up, because I'm trying to test my feature modules independently of the application, but I very quickly hit the DEX ceiling (espresso + mockito), so I wanted to ProGuard (quick dead code elimination only) the androidTest APK.
Here's to hoping it is an easy fix to enable this feature, as much as adding an `else if` somewhere.
Sidenote: I think in an ideal world there would be two switches minifyEnabled and testMinifyEnabled as I may want to not eliminate anything from my AAR, but I want to eliminate dead code / optimize the test APK, but I guess that's a different story to this bug.