Status Update
No update yet.
Comments
rp...@google.com
rp...@google.com
However, during predictive back animation the entering screen is drawn on top of the exiting screen as the video linked in the issue also reproduces
navigation library used: 2.8.0-alpha06
rp...@google.com
It looks like a possible root cause could be that the exiting destination is correctly drawn on top when there's a pop, but predictive back press isn't actually pop and therefore isn't drawn on top.
Most of the logic seems to check composeNavigator.isPop.value || inPredictiveBack, but targetZIndex only checks pop when it should instead probably check for either pop or inPredictiveBack?
be...@google.com
be...@google.com
Once a sample project is provided we will reopen this issue, as we cannot reproduce this at the moment.
rp...@google.com
I have created a sample project which reproduces the issue, and attached a video.
When enableOnBackInvokedCallback is enabled in manifest, the pop exiting destination is incorrectly drawn underneath the pop entering destination. When it is disabled, everything works as expected (but no predictive back)
Description
Android Gradle Plugin: 3.2.0-alpha16
Gradle: 4.6
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: 2.8.12.2;
Steps:
1. Create a new empty Activity project with AppCompat enabled
2. Go to generated styles.xml
3. Ctrl+click the DarkActionBar in 'Theme.AppCompat.Light.DarkActionBar'
4. This takes you inside the AppCompat aar's values.xml as expected (to the definition of Theme.AppCompat.Light.DarkActionBar)
5. From there, try to navigate further to the 'Base.Theme.AppCompat.Light.DarkActionBar'
Expected: Android Studio navigates to the clicked style (or suggests options if there are alternative resources)
Actual: Error message that says: 'Cannot find declaration to go to'
Additional info: This has worked before, so might have become broken after upgrading Studio at some point. I don't remember the exact version when it became broken though. But perhaps this is also some kind of indexing/cache issue, but I've at least tried to run File -> Invalidate caches / Restart to invalidate caches, but it does not help.