Fixed
Status Update
Comments
ku...@google.com <ku...@google.com>
gh...@google.com <gh...@google.com> #2
Will be this fix also part of 4.2 please?
gh...@google.com <gh...@google.com> #3
for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.
xo...@google.com <xo...@google.com> #4
I understand that if there is more transformer is necessary to make every folder different, but there is the main problem, that the final one (last transform) is inside of the intermediate folder. The last transformation should end in the standard location, right? Maybe also with the default name not?
gh...@google.com <gh...@google.com> #5
Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?
Description
AI-213.7172.25.2113.9123335, JRE 11.0.13+0-b1751.21-8125866x64 JetBrains s.r.o., OS Linux(amd64) v5.17.0-1020-oem, screens 1920.0x1080.0, 2560.0x1440.0
AS: Dolphin | 2021.3.1 Patch 1
Kotlin plugin: 213-1.7.20-release-for-android-studio-AS6777.52
Android Gradle Plugin: 7.3.1
Gradle: 7.4
Gradle JDK: version 11.0.13
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
In my build.grade file, I have specified a number of dependencies. In order to ensure that builds don't break when transitive dependencies change, I'm pinning the version of packages to build with. For example, I have:
"implementation 'androidx.appcompat:appcompat:1.5.1!!'"
What is strange is that Android Studio highlights this statement stating:
"A newer version of androidx.appcompat:appcompat than 1.5.1!! is available: 1.5.1"
It appears that the UI is doing a textual string comparison rather than a semantic version comparison. The pinned version is the latest available and should not be highlighted for action.