androidx.wear.protolayout:protolayout missing -material.

[DevronB]

Android framework version

net8.0-android

Affected platform version

34

Description

Wear.Tiles.Material has been deprecated and replaced with androidx.wear.protolayout:protolayout-material, but this package in not bound. Can we please get androidx.wear.protolayout:protolayout-material added.

thank you

Steps to Reproduce

no package

Did you find any workaround?

no

Relevant log output

[moljac]

Thanks for the feedback.

Most likely after nugets with net10.0 are published.

[DevronB]

you mean like end of year?

[moljac]

you mean like end of year?

Nope. Why would it be end of the year? Releasing nuget packages has nothing to do with .NET release cycle.

[DevronB]

Ok, I misunderstand. What's the rough timing then? I'm trying work out if I should persist with the deprecated methods or wait. Cheers

[moljac]

We alredy have nugets that have/carry both net8.0 (current) and net10.0 payloads (dlls), but need few more internal tests (MAUI) before releasing them into the wild.

So, it is matter of days or weeks (max, worst case)

[DevronB]

@moljac, any progress? ta

[moljac]

@moljac, any progress? ta

I am sorry, but no. Some unplanned events occured.

There is PR - WIP:

#1123

I am in process of returning hardware, getting new hardware, updating my CV and redume and searching for job.

I will do some updates over the summer and I might squeeze this in, but no promises.

[DevronB]

oh, sorry to hear that! Where does this leave the bindings, are you the only one?

What is the support model with these, is there no official MS support for these?

[moljac]

oh, sorry to hear that! Where does this leave the bindings, are you the only one?

No. Team was reduced from 7 to 2.

What is the support model with these, is there no official MS support for these?

I know I will help our team members as community, but cannot guarantee cadence as it used to be. Regarding support - I have no idea. You will have to ask decision makers and they do not hang around.

[DevronB]

I guess AI is going to do all the work now 😒

[jonathanpeppers]

If you want a new package for androidx.wear.protolayout:protolayout-material, one way to fast track this work is to send a pull request for the feature.

Even if it doesn't build or isn't complete. A pull request would help us a lot towards a new package! Simply starting the work, and saying: I got this far, here is the error.

In regards to "support", most support policies are around security vulnerabilities, etc. These packages are certainly still maintained in that regard. Thanks!

[DevronB]

@jonathanpeppers , thanks for the feedback! I was thinking it might be time to roll the sleeves up :-) now to get my head around these bindings, is there some sort of guide/best practice on addressing binidng issues?

[jonathanpeppers]

These are the best docs we have at the moment:

• https://learn.microsoft.com/en-us/dotnet/maui/migration/android-binding-projects
• https://github.com/dotnet/android-libraries/blob/main/BUILDING.md

In general, this repo controls a lot of the binding process with this file:

android-libraries/config.json

Lines 11 to 17 in 2bc0d31

	{
	"groupId": "androidx.activity",
	"artifactId": "activity",
	"version": "1.10.1",
	"nugetVersion": "1.10.1.1",
	"nugetId": "Xamarin.AndroidX.Activity"
	},

This .json file tells the build to look up a maven artifact, and it automatically generates a C# binding project.

This is would be different if you were making your own binding. They did it this way, so they could easily create 100s of NuGet packages.

[DevronB]

#1172

@jonathanpeppers @moljac