Status Update
Comments
es...@gmail.com <es...@gmail.com> #2
The attached Build Scan log shows that the emulator process crashed unexpectedly. Could you rerun your task with --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
to get more information about the emualtor process logs?
es...@gmail.com <es...@gmail.com> #4
No idea why the scan does not contain log information, here you are:
es...@gmail.com <es...@gmail.com> #5
The link in --info
and -Pandroid.experimental.testOptions.managedDevices.emulator.showKernelLogging=true
, the emulator process output its kernel logging to stdout. Do you see any stacktrace or segfault in the log?
ap...@google.com <ap...@google.com> #6
That's strange, the repo and the build is public... But I attached the logs as file
cl...@google.com <cl...@google.com>
es...@gmail.com <es...@gmail.com> #7
I looked into the logs and it turns out, the runner didn't have enough disk space. I guess the root cause is the Gradle update causing another Gradle major version (and its new transform-4) folder to cache was too much. Anyway, a better error message of the exit code of GMD would be helpful.
ap...@google.com <ap...@google.com> #8
Thanks for uploading the log! Yes, the emulator kernel log says the issue was the insufficient disk space:
2024-04-02T18:31:45.7078429Z ERROR | Not enough space to create userdata partition. Available: 7177.027344 MB at /home/runner/.config/.android/avd/gradle-managed/dev34_aosp_atd_x86_64_Pixel_2.avd, need 7372.800000 MB.
Also, I agreed that GMD should diagnose errors and can provide better messages.
Let me rename this issue's title to improve the error message for disk space error.
cl...@google.com <cl...@google.com> #9
I've added a fix that will surface all error messages from the emulator in the exception when it closes unexpectedly.
ap...@google.com <ap...@google.com> #10
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 2
- Android Gradle Plugin 8.9.0-alpha02
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!
ap...@google.com <ap...@google.com> #11
Project: platform/frameworks/support
Branch: androidx-main
Author: Clara Fok <
Link:
Update non-reified composable and navigation
Expand for full commit details
Update non-reified composable and navigation
Added <T : Any> type parameter to the API
Test: ./gradlew navigation:navigation-compose:cC
Bug: 366291612
Relnote: "Non-reified composable and navigation API expects route from KClass<T> instead of KClass<*>"
Change-Id: Icd47da4061103edd8462a729ae168e724d833d36
Files:
- M
navigation/navigation-compose/api/current.txt
- M
navigation/navigation-compose/api/restricted_current.txt
- M
navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavGraphBuilderTest.kt
- M
navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavGraphBuilder.kt
Hash: 653f2ea988ff3744ecf3de08c3221c4ee8c64917
Date: Wed Dec 04 13:41:46 2024
pr...@google.com <pr...@google.com> #12
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.navigation:navigation-common:2.9.0-alpha04
androidx.navigation:navigation-compose:2.9.0-alpha04
Description
Component used: Navigation Version used: 2.8.0
I'm currently using Voyager but decided to try migrating to Compose Navigation as it already provides better type-safety. However, I find it difficult to migrate since the Api is lacking in some way while there are some that are available but is only limited to the Library Scope.
This is in conjunction with Issue 361863272
I would like to request non-reified
navigation
,composable
, andNavBackStackEntry.toRoute()
wherein you can enter the class's KClass as a parameter.Voyager provides
Screen
, andTab
interfaces which could easily be implemented and extended to another interface or abstract class wherein you could create a common Class with common implementations you can tailor according to your needs. Compose Navigation currently doesn't support this but it is much more scalable especially with deeplinks.Migration to Compose Navigation without any interface proves to be difficult unless the above requested are given. I have here an example implementation of interfaces. I don't know how much effective it will be but technically it could be applied to my project to some extent since there are a lot of caveats I don't know of. It would be much better if Compose Team can provide similar interfaces which could greatly boost migration to the library.