AndroidX Tracking Bug: Support ArrayBuffers in WebMessage API [251152171]

Fixed

Feature Request

Status Update

No update yet.

Description

pb...@google.com

created issue #1

Oct 5, 2022 02:06PM

This is an AndroidX-side tracking bug for https://crbug.com/1023334

Design doc: https://docs.google.com/document/d/1nsQnwwY43OuA4PsSaMioiKA0c_M1eV1XX2q15YFA7cI/edit#heading=h.grah444pqbxl

Comments

li...@microsoft.com <li...@microsoft.com> #2Oct 6, 2022 01:46AM

It's failing when accessing androidx.navigation.compose.BackStackEntryIdViewModel

ap...@google.com <ap...@google.com> #3Oct 6, 2022 01:15PM

Repro of a public github project https://github.com/yschimke/wearwind/tree/navbug

na...@google.com <na...@google.com> #4Oct 24, 2022 01:37PM

Reproducible with navigation-compose:2.4.0-beta02, without hilt.

pb...@google.com <pb...@google.com> Apr 26, 2023 02:12PM

Accepted by li...@microsoft.com.

ap...@google.com <ap...@google.com> #5May 17, 2023 01:28AM

Could be related to this change https://android-review.googlesource.com/c/platform/frameworks/support/+/1843944 which pinned wear-compose to navigation 2.4.0-alpha10 (and it's still set to that version).

api("androidx.navigation:navigation-runtime:2.4.0-alpha10")

jo...@gmail.com <jo...@gmail.com> #6May 18, 2023 10:35PM

I built a version of androidx-main without pinning wear-compose to navigation 2.4.0-alpha10 (see comment#5) - still saw the same exception.

ap...@google.com <ap...@google.com> #7May 26, 2023 04:38PM

Marked as fixed.

pr...@google.com <pr...@google.com> #8Jun 8, 2023 01:30AM

Further info - if we revert the change mentioned in comment#5 (https://android-review.googlesource.com/c/platform/frameworks/support/+/1843944) then the androidx.wear.compose.navigation tests fail with the same exception: java.lang.IllegalStateException: You cannot access the NavBackStackEntry's ViewModels until it is added to the NavController's back stack (i.e., the Lifecycle of the NavBackStackEntry reaches the CREATED state)