-
Notifications
You must be signed in to change notification settings - Fork 533
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing androidx.window.[extensions|sidecar]
warnings
#6809
Comments
I've already reported this some time ago via #6375, the app still works for me even if you see the messages. |
I also see those
|
yes, this is new, but I also get it in VS2019 16.11.10 and started since last AndroidX Nuget updates from end of last week. |
@jpobst / @moljac would you know if there is something new about these libraries?
Would these be something new where you define |
We are tracking this in #6652. The IDE team have an internal ticket which they are working on. I'll keep #6652 as up to date as I can. |
@conceptdev Would you be so kind and help? Do you have any experience with this?
|
I cannot find these types in any of Google's AndroidX packages:
But the latest releases of AndroidX do now generally have a dependency on |
It's my understanding that the sidecar and extensions code are what we ship on device (ie. Surface Duo), to provide the OEM-specific implementation of the Window Manager dual-screen/foldable API surface. Other OEMS (like Samsung) would ship their own packages (again, in their OS). Android native (Kotlin/Java) apps that consume AndroidX Window Manager do not reference these libraries via gradle. Not sure where these warnings are coming from in Xamarin.Android. On maven.google.com I don't see corresponding packages there either. |
@jpobst do any of the |
Hmm, yes. The
|
@jonathanpeppers, @dellis1972, @jpobst From the comments above, it would seem that the androidx.window stuff is being addressed, however, there has been no mention of the conflict between the two versions of System.Numeric.Vectors or has it been addressed in another issue? |
The solution for this one is to use .NET 6 unfortunately. The problem here is that Mono has a different version of this assembly, and some package is trying to bring in a newer version from NuGet. |
For my project, upgrade Xamarin.AndroidX.Legacy.Support.V13 to newest 1.0.0.13 triggers the error, revert back to 1.0.0.12 and errors disappear. |
Confirmed that version 1.0.0.12 on the Xamarin.AndroidX.Legacy.SupportV4 also makes this error go away. 1.0.0.13 has quite the breaking change for a point release. |
Which error are you referring to? This issue lists 2 new warnings. |
For me it's the two XA4218 missing jars. androidx.window.sidecar.jar and androidx.window.extensions.jar |
@jpobst |
Sec! Missing Official google maven does not mention https://maven.google.com/web/index.html?q=androidx.window#androidx.window if you step out of Microsoft world there are few pointers (though there is MS FTE working on the issue): In https://groups.google.com/a/chromium.org/g/java/c/bf9if0l3VJ4?pli=1 there is explanation (seems like internal classes and interfaces, kotlin vs java and R8/proguard tooling) and horrible workaround. Seems that problem is 2+ years old. Seems our tooling just got better with surfacing warnings too. |
Also related; |
@jonathanpeppers @jpobst TL&DR; where would:
come from??? |
It was the ones I googled for that got me to this thread.
These were not files I intentionally included. So something changed between the 1.0.0.12 and 1.0.0.13 releases that caused this since reverting made the error go away. |
These warnings are coming from AndroidX ( |
Not good practice to simply 'ignore warnings'. Not how I like to write my programs. Thank you for your opinion. |
It comes from Xamarin.AndroidX.Window. Most Android apps will eventually depend on this package through a long enough dependency chain:
|
What about We'd have to change something in Xamarin.Android to fix our warning, it could probably check the |
It might fix one of the warnings, but not the Maybe we should be looking at the <uses-library
android:name="androidx.window.extensions"
android:required="false" /> Granted, that's why it's only a warning and not an error. |
Maybe when these libraries are stable Google will add them to |
Maybe we should not emit the warning when we cannot find the library in |
I would not do that. Warnings are not caused by us.
This leads to correct official location https://maven.google.com/web/index.html?q=androidx.window#androidx.window:window-extensions
No. It was bound when https://github.com/xamarin/AndroidX/blob/main/config.json#L1325-L1348 see my comment: |
the warnings are still present in Visual Studio Version 17.3.0 Preview 6.0 |
Thanks for the feedback, but Visual Studio version has nothing to do with this issue. See: #6809 (comment) |
androidx.window.[extensions|sidecar]
warnings
I have the same warnings after upgrading the project to a newer Xamarin version using VS 17.5.2. I didn't have the |
Both warnings are still present after migrating a Xamarin.Android app to .NET 8 |
Fixes dotnet#6809 We have an issues where if a library manifest contains the following element and the file dos NOT exist in `android-sdk\platforms\android-XX\optional` we get an XA4218 warning. ```xml <uses-library android:name="androidx.window.sidecar" android:required="false" /> ``` This is the warning. ``` Warning XA4218: Unable to find //manifest/application/uses-library at path: android-sdk\platforms\android-31\optional\androidx.window.sidecar.jar obj\Release\120\android\AndroidManifest.xml ``` So the work around this issue if the `required` attribute is NOT `true` we should ignore the warning. If the library is `required`` or the `required` attribute is NOT specified we should revert to to the current behavior. This warnings can come up if people use vendor specific .aar files. The libraries they are referring too will never exist in the `sdk` `optional` folder.
Fixes dotnet#6809 We have an issues where if a library manifest contains the following element and the file dos NOT exist in `android-sdk\platforms\android-XX\optional` we get an XA4218 warning. ```xml <uses-library android:name="androidx.window.sidecar" android:required="false" /> ``` This is the warning. ``` Warning XA4218: Unable to find //manifest/application/uses-library at path: android-sdk\platforms\android-31\optional\androidx.window.sidecar.jar obj\Release\120\android\AndroidManifest.xml ``` So the work around this issue if the `required` attribute is NOT `true` we should ignore the warning. If the library is `required`` or the `required` attribute is NOT specified we should revert to to the current behavior. This warnings can come up if people use vendor specific .aar files. The libraries they are referring too will never exist in the `sdk` `optional` folder.
Fixes dotnet#6809 We have an issues where if a library manifest contains the following element and the file dos NOT exist in `android-sdk\platforms\android-XX\optional` we get an XA4218 warning. ```xml <uses-library android:name="androidx.window.sidecar" android:required="false" /> ``` This is the warning. ``` Warning XA4218: Unable to find //manifest/application/uses-library at path: android-sdk\platforms\android-31\optional\androidx.window.sidecar.jar obj\Release\120\android\AndroidManifest.xml ``` So the work around this issue if the `required` attribute is NOT `true` we should ignore the warning. If the library is `required`` or the `required` attribute is NOT specified we should revert to to the current behavior. This warnings can come up if people use vendor specific .aar files. The libraries they are referring too will never exist in the `sdk` `optional` folder.
Fixes dotnet#6809 We have an issues where if a library manifest contains the following element and the file dos NOT exist in `android-sdk\platforms\android-XX\optional` we get an XA4218 warning. ```xml <uses-library android:name="androidx.window.sidecar" android:required="false" /> ``` This is the warning. ``` Warning XA4218: Unable to find //manifest/application/uses-library at path: android-sdk\platforms\android-31\optional\androidx.window.sidecar.jar obj\Release\120\android\AndroidManifest.xml ``` So the work around this issue if the `required` attribute is NOT `true` we should ignore the warning. If the library is `required`` or the `required` attribute is NOT specified we should revert to to the current behavior. This warnings can come up if people use vendor specific .aar files. The libraries they are referring too will never exist in the `sdk` `optional` folder.
Android application type
Classic Xamarin.Android (MonoAndroid12.0, etc.)
Affected platform version
VS2022 17.2.0 Preview 1.0
Description
After upgrading all my nugets to the latest versions, the following are new warnings.
Also attaching the MS Build log. Do you need anything else from me?
Could you please advise about the following, where it comes from etc?
Missing class androidx.window.extensions.WindowExtensions (referenced from: androidx.window.extensions.embedding.ActivityEmbeddingComponent
Build04032022.zip
Steps to Reproduce
N/A
Did you find any workaround?
The app deploys and runs just fine.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: