Jonathan Peppers

@igorboskovic3 we had 3 reports come in related to this in the past 24 hours, let me know if there is anything I can do to help, thanks!

Xamarin.Android 13 released to stable yesterday along with VS 2022 17.3: * https://download.visualstudio.microsoft.com/download/pr/e81e04d3-768a-4310-9c9b-f32e8ba00eaa/cadb090bcfdea3e663e23d082701d4ad/xamarin.android-13.0.0.0.pkg * https://download.visualstudio.microsoft.com/download/pr/f33785ca-afdb-403b-a9aa-1465b7c2737c/7261c190c51cfa50126fce083b5ebee54542ac6a8816880bfc3474b7d9830284/Xamarin.Android.Sdk-13.0.0.0.vsix

FYI I reviewed the contents of this file again: /Library/Frameworks/Xamarin.Android.framework/Versions/Current/lib/xamarin.android/xbuild/Xamarin/Android/Xamarin.Android.Common.props The image seems like it has: ```xml 12.0.0-3 ``` So the only "mismatch" I actually see, is in a customer's...

I believe https://github.com/actions/runner-images/pull/6045 is updating the image, maybe @al-cheb can comment how long that will take to roll out everywhere.

@al-cheb we have a customer saying they still don't have Xamarin.Android 13.x on `macos-latest`: https://github.com/xamarin/xamarin-android/issues/7233#issuecomment-1233315111 Is there more info we can ask for? I wonder if they somehow don't have...

Looks like Glide has a Java sample using SVG files [here](https://github.com/bumptech/glide/tree/master/samples/svg/src/main/java/com/bumptech/glide/samples/svg). But it looks like you have to write a bunch of code to make it work... Parts of Glide...

@themronion can you share a link of what you are referring to? Xamarin.Android does not have Java annotation support.

Ok yeah, @themronion this looks like it is using `` that came with the new shapes features in Xamarin.Forms 4.8. I would use `` directly for an `.svg` file, that...

Can you share an example code snippet that fails? Maybe you could add a page to this app? https://github.com/jonathanpeppers/glidex/tree/master/glidex.forms.sample/Forms Thanks!

@visualbruno if you fixed something, would you consider sending a pull request explaining the fix? Thanks!