Update layoutlib to v14.0.9 (Koala Feature Drop +)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.android.tools.layoutlib:layoutlib-runtime (source)	14.0.8 -> 14.0.9
com.android.tools.layoutlib:layoutlib-resources (source)	14.0.8 -> 14.0.9
com.android.tools.layoutlib:layoutlib (source)	14.0.8 -> 14.0.9

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[geoff-powell]

Looks like the only failing test is the widgets project. Seems like the navigation icons changed. 🤔

Before

After

Diff

[geoff-powell]

Update here, I think this bump in layoutlib is tied to AS Koala Feature Drop release.

Looking in Jellyfish AS instance the previous navigation icons are shown.

When opening Koala 2024.2.1 (feature drop) the navigation icons have changed. So I am assuming that this version 14.0.9 is using layoutlib version used in that version or later. [still need to test AS Ladybug]

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[jrodbx]

Suggested change

	// When using Dialogs in Compose, it seems that a WindowManager view gets added to the view group alongside the ComposeView under test.
	// When our view under test is removed, compose will remove the WindowManager view first and then the ComposeView. But since the index of the view under test is 1
	// and there are only 1 views in the ViewGroup when WindowManager is removed, it throws an invalid index.

good context for a PR comment today. But it's not a controversial code change (worst case, it's defensive) and the code comment will likely grow stale if Compose implementation details change.

[geoff-powell]

good point, I will move this to a PR comment for context.

      // When using Dialogs in Compose, it seems that a WindowManager view gets added to the view group alongside the ComposeView under test.
      // When our view under test is removed, compose will remove the WindowManager view first and then the ComposeView. But since the index of the view under test is 1
      // and there are only 1 views in the ViewGroup when WindowManager is removed, it throws an invalid index.
      

[geoff-powell]

@jrodbx curious, now that we are using the provided google artifacts for layoutlib, do you know if we can pull which version of AS corresponds with?

[jrodbx]

@jrodbx curious, now that we are using the provided google artifacts for layoutlib, do you know if we can pull which version of AS corresponds with?

AFAIK, there's no simple way to extract that programmatically. However, I have asked for that very mapping and an issue has been filed here.

[geoff-powell]

@jrodbx curious, now that we are using the provided google artifacts for layoutlib, do you know if we can pull which version of AS corresponds with?

AFAIK, there's no simple way to extract that programmatically. However, I have asked for that very mapping and an issue has been filed here.

cool, +1'd the filed issue