Fixed
Status Update
Comments
je...@google.com <je...@google.com>
al...@google.com <al...@google.com> #2
I also have the same issue so it seems to be a real problem.
al...@google.com <al...@google.com>
al...@google.com <al...@google.com>
xa...@google.com <xa...@google.com> #4
why is this marked has Obsolete? this is still a bug that is happening and its difficult to fix.
for all who are looking for a solution use this:
http://stackoverflow.com/questions/16200972/android-css-positionfixed-after-a-device-rotate
for all who are looking for a solution use this:
sa...@google.com <sa...@google.com> #5
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Electric Eel Beta 4 (2022.1.1.14)
- Android Gradle Plugin 7.4.0-beta04
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
sa...@google.com <sa...@google.com> #6
Further fixes for this issue are now available in:
- Android Studio Flamingo Canary 7 (2022.2.1.7)
- Android Gradle Plugin 8.0.0-alpha07
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Description
Using a basic project with 1 app and 1 lib, using AGP 7.4.0 alpha 2, we see the following manifest files after a build:
The fact that we have 3 intermediate manifests in the app and (more importantly) 2 in the library is probably something we can optimize, in some cases.
The most important aspect here is the library as we need this for scaling. If the reason to have 2 is something we can put behind an opt-in feature that would be better.