Fixed
Status Update
No update yet.
Comments
to...@gmail.com
.
to...@gmail.com
.
ti...@google.com
to...@gmail.com
We're unable to reproduce this issue on Android Studio Canary 13.
Android Studio Arctic Fox | 2020.3.1 Canary 13
Build #AI-203.7148.57.2031.7242491, built on March 29, 2021
Runtime version: 11.0.8+0-b944-P17168821 amd64
Android Studio Arctic Fox | 2020.3.1 Canary 13
Build #AI-203.7148.57.2031.7242491, built on March 29, 2021
Runtime version: 11.0.8+0-b944-P17168821 amd64
to...@gmail.com
@4 OK updated to this now. Very easy to reproduce again.
See attached of how to reproduce it on canary 13 too:
Android Studio Arctic Fox | 2020.3.1 Canary 13
Build #AI-203.7148.57.2031.7242491, built on March 29, 2021
Runtime version: 11.0.8+10-b944.6842174 amd64
VM: OpenJDK 64-Bit Server VM by N/A
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4000M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: Show As ..., String Manipulation, com.dubreuia, com.intellij.marketplace, org.jetbrains.kotlin, com.google.mad-scorecard, org.intellij.plugins.markdown
See attached of how to reproduce it on canary 13 too:
Android Studio Arctic Fox | 2020.3.1 Canary 13
Build #AI-203.7148.57.2031.7242491, built on March 29, 2021
Runtime version: 11.0.8+10-b944.6842174 amd64
VM: OpenJDK 64-Bit Server VM by N/A
Windows 10 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4000M
Cores: 12
Registry: external.system.auto.import.disabled=true, ide.settings.move.mouse.on.default.button=true, debugger.watches.in.variables=false
Non-Bundled Plugins: Show As ..., String Manipulation, com.dubreuia, com.intellij.marketplace, org.jetbrains.kotlin, com.google.mad-scorecard, org.intellij.plugins.markdown
to...@gmail.com
Is it still reproducible with the new Logcat in Studio Electric Eel?
to...@gmail.com
@6 You've deleted all the files I've uploaded here (or the website has). How can I check it out?
I don't remember what was written on the project a year ago...
Please restore the files so that I could check it out.
Also please stop deleting my files.
I don't remember what was written on the project a year ago...
Please restore the files so that I could check it out.
Also please stop deleting my files.
ti...@google.com
The files were deleted due to expiration of the retention period for restricted attachments. They are not recoverable.
ap...@google.com
@8 So disable this behavior or extend it to enough time till you answer and I can check it out.
Otherwise there is no point in writing here as you answer too late for me to check it out again, because you don't give me a chance to do it.
Otherwise there is no point in writing here as you answer too late for me to check it out again, because you don't give me a chance to do it.
ti...@google.com
Sorry it took us so long to address this bug. That said, the Logcat tool window was rewritten from scratch so this bug is no longer relevant.
to...@gmail.com
@10 OK.
Can you please fix the way it shows the text, though?
I mean this:
https://issuetracker.google.com/issues/258484270
Many times I forget it even exists, and I see the time instead of the text that I printed...
Can you please fix the way it shows the text, though?
I mean this:
Many times I forget it even exists, and I see the time instead of the text that I printed...
pr...@google.com
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.compose.animation:animation:1.8.0-alpha05androidx.compose.animation:animation-android:1.8.0-alpha05androidx.compose.animation:animation-jvmstubs:1.8.0-alpha05androidx.compose.animation:animation-linuxx64stubs:1.8.0-alpha05
Description
Jetpack Compose version: 1.8 snapshots starting with 12408595 (So included in alpha03)
I unfortunately have some trouble to build a small repro but that commit broke transitions handled by
AnimatedContentin my app.See attached video.
There's also some details in slack in a thread with Doris.
To resume, there's some size resolution issues when removing and adding back screens that makes the
AnimatedContentwrongly detect a size change and doing wrong size animations.You can see in the video that the fade transition does work, then when switching screen then going back it no more work correctly and animate the size for no reasons.
Forcing
.using(null)does workaround the issue.When reaching the broken state, if both contents of
AnimatedContentare boxes with.fillMaxSize()then it just shows a black screen as is it was animating from 0 to 0 size. If one of the content does not have the.fillMaxSize()then it leads to the size animations you can see in the video.