[Bug]: Why is currentDestination momentarily returned as null ?

[mahmed1987]

Is there an existing issue for this?

• I have searched the existing issues

Is there a StackOverflow question about this issue?

• I have searched StackOverflow

What happened?

When switching between the top level destinations , why is the current destination null first , and later gets its actual value ? This causes a flicker when moving from screen to screen since when the destination is null the top bar is taken out of the composition tree , and later bought back in

Just navigate to this location in NIA
com/google/samples/apps/nowinandroid/ui/NiaApp.kt:203
and add a Log statement under destination property
Log.d("Current Destination ","${destination}")

I have pasted the LogCat result too .

Also attached is a video in which the flicker can be clearly observed .

This is a huge issue and I am pretty sure this didn't exist when using navigation via string routes.

Please advise .

Now.in.Android.screen.recording.mp4

Relevant logcat output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct