Closed ColtonIdle closed 1 month ago
Hi @ColtonIdle,
I see that you deleted a template 😢, please don't do that. Based on the video, I'd say that it's an Android device emulator. LIke in Compose itself, we're using original Google binaries on Android, so it means that the issue is not in our fork and should be reported to Google issue tracker.
Regarding the reproduction itself. The content is still interactable during transaction animation (it's expected). You can add a check based on the lifecycle state to prevent this:
if (lifecycle.currentState < Lifecycle.State.RESUMED) {
// Application is not in focus or navigation transition is in progress
return
}
Sorry, for not going by the template. I wasn't sure where to put this ticket so I just wanted to get a feel for where it should go so I didn't want to spend the time filling in a bunch of details in case this was the wrong repo (first time trying to submit a bug for androidx/kmp stuff)
Seems like this might have been the right repo then? 😄
For what its worth... I submitted to android's issuetracker but it was closed as
Issues with org.jetbrains.androidx.navigation:navigation-compose" should be filed against the Jetbrains tracker, thanks!
See: https://issuetracker.google.com/issues/341973424
Please let me know what you think I should do next. The issue also happens on iOS. I can try to request for it to be re-opened on the Android side if that's what you think.
I can understand the confusion there, but I believe it was the right place. I'll discuss this with Google folks internally
Please let me know what you think I should do next. The issue also happens on iOS. I can try to request for it to be re-opened on the Android side if that's what you think.
Since the issue happens on Android, it's about the original library and can be reproduced without a multiplatform adoption. So you can add a reproduction with Google's only dependencies to that issue.
Got it. I will try! And my apologies... Was just trying to be helpful!
Sent from Proton Mail Android
-------- Original Message -------- On 5/23/24 4:15 AM, Ivan Matkov wrote:
I can understand the confusion there, but I believe it was the right place. I'll discuss this with Google folks internally
Please let me know what you think I should do next. The issue also happens on iOS. I can try to request for it to be re-opened on the Android side if that's what you think.
Since the issue happens on Android, it's about the original library and can be reproduced without a multiplatform adoption. So you can add a reproduction with Google's only dependencies to that issue.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.***>
Two distinct issues.
Description of Video: 1-15 seconds. showing happy path of going to next screens. then mashing back. everything works fine. 15-26: Trying to show the flashing that appears in issue 1 26-33: Showing that mashing back button sometimes leave you in a bad state
Code is pretty simple
Here is a video https://github.com/JetBrains/compose-multiplatform/assets/31751141/c176a65e-ffe2-4fa0-a66f-4697f7e65282