Move Animation APIs from Accompanist back into Jetpack Navigation [197140101]

Fixed

Feature Request

Status Update

No update yet.

Description

jb...@google.com

created issue #1

Aug 18, 2021 08:31PM

As of compose 1.0.1 many of the Compose Animation APIs are still @Experimental.

Because of AndroidX internal restrictions, modules cannot depend on experimental APIs from other modules.

In the interest of providing a solution for Navigation with custom Compose Animations as soon as possible, we opted to provide a new module in Accompanist Navigation. Once all the required animation APIs become stable, which is planned as part of Compose 1.1.0, we will move the implementation back into the Jetpack Navigation library from Accompanist Navigation Animation.

For more details, see the Animations in Navigation Compose blog post.

Comments

ti...@gmail.com <ti...@gmail.com> #2Feb 12, 2022 08:03PM

does 31.1.x have this flicking problem ?

il...@google.com <il...@google.com> #3Feb 14, 2022 05:19PM

Hi, are you using emulator in a tool window or the standalone emulator?

ti...@gmail.com <ti...@gmail.com> #4Aug 2, 2022 04:09PM

using emulator in tool window.

ru...@gmail.com <ru...@gmail.com> #5Jan 25, 2023 06:32AM

Carlos,

would you help to see if you could repro this issue? Please try to use an nVidia GeForce graphics card if possible.

k8...@gmail.com <k8...@gmail.com> #6Mar 21, 2023 02:11PM

We have had this issue too. Appears on NVIDIA graphics, various different computers. Does not happen with the prior emulator version 31.x, occurs using system image 30 as above. We are using the emulator standalone.

Found it occurs mostly when there is another OpenGL/3D app (Unity) running on the computer at the same time.

il...@google.com <il...@google.com> #7Mar 21, 2023 04:16PM

Thank you for your report. That would help us isolating the issue.

jb...@google.com <jb...@google.com> May 8, 2023 06:11PM

Reassigned to cl...@google.com.

ap...@google.com <ap...@google.com> #8May 11, 2023 04:32PM

I can't reproduce this on our corp machine that uses an Nvidia Quadro P1000 on 511.09 drivers but on my personal machine running an RTX 2080 Super on 512.15 drivers, I'm experiencing some graphical artifacts as shown in the attached video. Is this similar to what everyone is experiencing?

ap...@google.com <ap...@google.com> #9May 11, 2023 04:32PM

Hi Carlos,

would you help to test if this build fixes the issue?

https://android-build.googleplex.com/builds/pending/P50592976/emulator-windows_x64/latest/sdk-repo-windows-emulator-P50592976.zip

ap...@google.com <ap...@google.com> #10May 11, 2023 04:32PM

I have tried that Build and the Emulator version that had the issue but can no longer reproduce them. I have also tried running Unity programs as suggest by

comment #6

but It seems it is an issue that is not as easily reproducible.

ap...@google.com <ap...@google.com> #11May 11, 2023 04:32PM

Hi Devki,

Would you help to cp the following to the next stable and canary? Thanks!

https://android-review.git.corp.google.com/q/topic:%22no-window%22

ap...@google.com <ap...@google.com> #12May 11, 2023 04:32PM

Ranjit, can you please help verify this in 32.1.12 stable and 33.1.3 canary?

il...@google.com <il...@google.com> #13May 11, 2023 11:12PM

Marked as fixed.

Hi

I was also experiencing this issue on my Nvidia 1660 Super Graphics card, on the latest 32.1.12 stable.

I can confirm that using the 33.1.2 canary (I wasn't able to find the 33.1.3 canary publicly) appears to have fixed the issue.