Fixed
Status Update
No update yet.
Comments
gh...@google.com
je...@google.com
st...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Are you reporting this as a Developer or User?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android build
Which Android build are you using? (e.g. UQ1A.240205.002)
Device used
Which device did you use to reproduce this issue?
Are you reporting this as a Developer or User?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report to google drive and share the folder to android-bugreport@google.com, then share the link here.
st...@google.com
Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.
da...@google.com
We are closing this issue since we didn't receive a response. If you are still facing this problem, please open a new issue and add the relevant information along with reference to this issue.
jo...@google.com
Bumping pri\sev because it would also break module-to-module dependency
jo...@google.com
This should be fixed now (Internal Change-Id: Iecb3fc78d5322d3f1239326e3738fe00e13bcd1b). It will arrive in AGP 8.0 (Flamingo)
Description
AI-201.8743.12.41.7199119, JRE 1.8.0_242-release-1644-b3-6222593x64 JetBrains s.r.o, OS Linux(amd64) v5.11.0-18-generic, screens 5120x2880, 5120x2880
AS: 4.1.3; Kotlin plugin: 1.4.32-release-Studio4.1-1; Android Gradle Plugin: 4.1.3; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.6.2
We are using prefab to package a native-only library in a submodule of our project that is then referenced as a dependency of our main application module. We have found that the first build works fine but subsequent builds don't because, even though any changes get compiled into new shared object files, those shared object files aren't being packaged into the AAR. Instead, the stale asset is used and the new changes aren't reflected in the build.
Currently, we are using a workaround where we automatically delete the build/intermediates/prefab_package directory in a Gradle preBuild step. This seems to fix the problem, but shouldn't be necessary.