Improve error messaging for NavController.getBackStackEntry when no destination is found [168311416]

Fixed

Bug

Status Update

No update yet.

Description

sk...@gmail.com

created issue #1

Sep 11, 2020 10:43PM

Component used: Navigation
Version used: 2.3.0

While using `by navGraphViewModels`, my crash reporting reports an error when invoked

NavGraphViewModelLazy.kt line 56
Fatal Exception: java.lang.IllegalArgumentException: No destination with ID 2131296839 is on the NavController's back stack
at androidx.navigation.NavController.getBackStackEntry(NavController.java:1293)
at com.example.ExampleFragment$$special$$inlined$navGraphViewModels$1.invoke(NavGraphViewModelLazy.kt:56)
[...]

This is difficult to debug since the navGraphId that I pass in should theoretically always be in the NavController's back stack when navGraphViewModels is invoked. The error message could be improved by letting me know what IS available on the back stack or if the back stack is completely empty.

Comments

il...@google.com <il...@google.com> Sep 14, 2020 11:11PM

Assigned to il...@google.com.

ap...@google.com <ap...@google.com> #2Sep 15, 2020 12:14AM

Hi, some users reported that installing "Vulkan SDK" helps with this issue. What is your GPU and its driver versions?

il...@google.com <il...@google.com> #3Sep 15, 2020 12:20AM

Marked as fixed.

WARN - Emulator: Pixel 9 Pro XL API 35 - Vanguard anti-cheat software is detected on your system. It is known to have compatibility issues with Android emulator. It is recommended to uninstall or deactivate Vanguard anti-cheat software while running Android emulator.
2024-12-03 13:34:02,503 [ 53041] INFO - #com.android.adblib.impl.SessionDeviceTracker - trackDevices() failed, will retry in 2000 millis, connection id=32
java.lang.IllegalStateException: ADB location has not been initialized

ap...@google.com <ap...@google.com> #4Sep 24, 2020 08:46AM

Hi, I have installed the Vulkan SDK on my PC, and my GPU is an NVIDIA GeForce RTX 3060 Laptop GPU with driver version 30.0.15.1274. I also tried deactivating the Vanguard anti-cheat, but the AVD still terminated. I’ve attached the log file after deactivating Vanguard.

Regarding the ADB issue ("ADB location has not been initialized"), I ran the adb version command in Command Prompt and successfully retrieved the version. Could you help me check this again?

ap...@google.com <ap...@google.com> #5Sep 24, 2020 08:52AM

Could you please try stating the Emulator from the command line this way

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
emulator.exe -avd Pixel_9_Pro_XL_API_33 -wipe-data -no-snapshot -verbose -feature -Vulkan

and attach its output? If you notice any popups about missing dlls please include them here.

ap...@google.com <ap...@google.com> #6Sep 24, 2020 08:57AM

Hi this is the output txt flle

ap...@google.com <ap...@google.com> #7Sep 24, 2020 09:18AM

Thank you, please try adding -gpu swangle (this is a software GPU, it will be slow), I think for whatever reason we can't talk to your GPU.

Please consider trying the latest version we have here:

https://developer.android.com/studio/emulator_archive

ap...@google.com <ap...@google.com> #8Sep 24, 2020 09:34AM

The attached TXT file contains the output after adding -gpu swangle. Following that, I manually updated the emulator from Android Emulator (35.2.10) Stable to Android Emulator (35.4.3) Canary. I also deleted the old AVD and created a new one, but it still terminated. I’ve attached the report generated after updating the emulator version.

Could you please check this for me?

ap...@google.com <ap...@google.com> #9Sep 24, 2020 09:36AM

DEBUG | emuglConfig_get_vulkan_hardware_gpu: Physical devices count is 0

Serdar, could you please take a look?

ap...@google.com <ap...@google.com> #10Sep 24, 2020 10:08AM

Please check if you have crashreports and if you do consider uploading them (please attach crash ids here):

cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator
crashreport.exe -l
crashreport.exe -u

ap...@google.com <ap...@google.com> #11Sep 24, 2020 10:10AM

Hi this is the output crash id :

Microsoft Windows [Version 10.0.19045.5131]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -l
C:\Users\crazy\AppData\Local\Temp\\AndroidEmulator\emu-crash-35.4.3.db\reports\fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a.dmp

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>crashreport.exe -u
Report fa3cbbcf-3433-4a63-9c3a-f4d9f8ba847a is available remotely as: 9a9150ec7b65047e

C:\Users\crazy\Desktop\CODING\AndroidSDK\emulator>

ap...@google.com <ap...@google.com> #12Sep 24, 2020 11:30AM

Thank you a lot! We got the crash. I think we can't handle zero of VK devices well :) Serdar should know more why we get zero VK devices.

https://android.googlesource.com/platform/external/qemu/+/refs/heads/emu-master-dev/android/android-ui/modules/aemu-gl-init/src/android/opengl/emugl_config.cpp#525

Maybe we should return false if deviceCount is zero.

ap...@google.com <ap...@google.com> #13Sep 24, 2020 11:32AM

Does this look related?

https://github.com/KhronosGroup/Vulkan-Loader/issues/552

ap...@google.com <ap...@google.com> #14Sep 24, 2020 11:52AM

I’m not entirely sure if it’s directly related to the issue I’m facing. If it is, what solutions would you recommend to address this? So far, I’ve noticed that deviceCount is zero, and I suspect it could be related to the Vulkan loader not detecting any devices.

If you have any specific steps or fixes in mind, I’d appreciate your guidance. I can also run additional tests like vulkaninfo or check my Vulkan configuration if needed.

vi...@gws.hotstar.com <vi...@gws.hotstar.com> #15Jun 22, 2022 09:53AM

As I understand, Vulkan-Loader/issues/552 is talking about the case when there are two GPUs: an integrated AMD and a separate NVIDIA and somehow the AMD side prevents returning anything. If this is your case, I think the solution is to update the AMD GPU drivers.

al...@gmail.com <al...@gmail.com> #16Aug 11, 2022 06:53AM

Hi bro, the AVD is working now! After uninstalling the driver and reinstalling the latest version, the AVD opens successfully. Thank you so much for your help and for taking the time to assist me!

jb...@google.com <jb...@google.com> #17Aug 11, 2022 07:06PM

Thank you for confirming this. We will fix the crash, but all we can do is to say "Your system has no Vulkan devices, update drivers or something" and exit.

sh...@gmail.com <sh...@gmail.com> #18Dec 27, 2022 01:05PM

Thank you for the update.

wm...@gmail.com <wm...@gmail.com> #19Apr 6, 2023 12:59PM

Thanks for reporting this, a change is submitted (aosp/3393546) and will be available in the next canary builds of the emulator to correctly give an error for zero device cases. I'll close this one now as the booting issue is resolved with a driver update.

ze...@gmail.com <ze...@gmail.com> #20May 31, 2023 03:51PM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Emulator 35.3.11 Stable

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

ir...@gmail.com <ir...@gmail.com> #21Nov 3, 2023 08:45PM

Further fixes for this issue are now available in:

Android Emulator 35.4.5 Canary