You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Shadow.Radius on Android13 [API 33] is broken #10401
Hi @jsuarezruiz, any news regarding this issue? Unfortunately, it is quite detrimental to my (and I'm sure many others) apps' design which was scheduled to be released for production this month.
Hi @@Stedy59. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.
You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Hi @Stedy59. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.
You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
Confirming this is still reproducing today on a recent .NET MAUI/.NET version, on a Samsung Android 13 device (API 33) — matches @GlacierFox's report above about the OEM build never picking up the Google BlurMaskFilter fix.
Environment
Microsoft.Maui.Controls 10.0.100
.NET SDK 10.0.400
net10.0-android
Repro: a Shadow with a negative Offset (so it bleeds outside the casting view's own bounds, e.g. Offset="0,-10") applied to a Grid, at low Opacity (~0.1). Expected a soft, gradually-fading darken of the adjacent content; actual result is a flat, hard-edged, uniformly-colored band with no visible blur regardless of Radius.
One data point that may help narrow down a workaround for affected OEM builds: per the discussion here and in #26789, switching the shadow-casting element from a Grid/BoxView to a Border with a solid (opaque, StrokeThickness="0") background appears to take the Canvas-drawn "solid shape" shadow path rather than the bitmap/BlurMaskFilter path — worth calling out in the docs/workaround guidance for anyone hitting this on affected devices, since Grid/BoxView are easy to reach for and don't get that fast path.
Thanks for keeping this open and triaged — happy to provide more repro detail if useful.
Follow-up: tested switching the shadow-casting element from a Grid to a Border with a solid, opaque, no-stroke background (per the discussion above and #26789) on the same affected Samsung Android 13 device. It did not resolve the issue — the shadow still renders as a flat, hard-edged band. Additionally, testing against a background that already has a light color tint nearby (not just plain white) made no visible difference either — the band looks equally solid/opaque either way, which suggests Opacity may not be respected at all on this device path, not just blur/Radius. Wanted to correct my earlier comment before it misleads anyone into thinking the Border workaround is reliable — for us it wasn't.
Activity
jsuarezruiz commentedon Sep 30, 2022
https://issuetracker.google.com/issues/244121207
jsuarezruiz commentedon Nov 18, 2022
https://issuetracker.google.com/issues/238769745
jsuarezruiz commentedon Nov 18, 2022
The TP1A.220905 build fixed that problem.
Mous625 commentedon Nov 24, 2022
Hi @jsuarezruiz, any news regarding this issue? Unfortunately, it is quite detrimental to my (and I'm sure many others) apps' design which was scheduled to be released for production this month.
Stedy59 commentedon Nov 28, 2022
I checked against the new API 33 build and all was good. When will MS push out this new emulator build?
Mous625 commentedon Nov 28, 2022
@Stedy59 as far as I know the issue is only present in Android 13 - API 33
Stedy59 commentedon Nov 28, 2022
Switch your Android SDK Manager to the Google feed and update your Android 13 - API33 emulator build to v7.
That version includes the Android OS fix.
Mous625 commentedon Nov 28, 2022
@Stedy59 Indeed it fixes the issue (on emulator).
27 remaining items
albyrock87 commentedon Jan 15, 2025
#26789 will avoid shadow bitmaps if your
Borderuses a solid background.dotnet-policy-service commentedon Aug 13, 2026
Hi @@Stedy59. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.
You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
dotnet-policy-service commentedon Aug 13, 2026
Hi @Stedy59. We have added the "s/try-latest-version" label to this issue, which indicates that we'd like you to try and reproduce this issue on the latest available public version. This can happen because we think that this issue was fixed in a version that has just been released, or the information provided by you indicates that you might be working with an older version.
You can install the latest version by installing the latest Visual Studio (Preview) with the .NET MAUI workload installed. If the issue still persists, please let us know with any additional details and ideally a reproduction project provided through a GitHub repository.
This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.
bobby-asure commentedon Sep 4, 2026
Confirming this is still reproducing today on a recent .NET MAUI/.NET version, on a Samsung Android 13 device (API 33) — matches @GlacierFox's report above about the OEM build never picking up the Google
BlurMaskFilterfix.Environment
net10.0-androidRepro: a
Shadowwith a negativeOffset(so it bleeds outside the casting view's own bounds, e.g.Offset="0,-10") applied to aGrid, at lowOpacity(~0.1). Expected a soft, gradually-fading darken of the adjacent content; actual result is a flat, hard-edged, uniformly-colored band with no visible blur regardless ofRadius.One data point that may help narrow down a workaround for affected OEM builds: per the discussion here and in #26789, switching the shadow-casting element from a
Grid/BoxViewto aBorderwith a solid (opaque,StrokeThickness="0") background appears to take the Canvas-drawn "solid shape" shadow path rather than the bitmap/BlurMaskFilterpath — worth calling out in the docs/workaround guidance for anyone hitting this on affected devices, sinceGrid/BoxVieware easy to reach for and don't get that fast path.Thanks for keeping this open and triaged — happy to provide more repro detail if useful.
bobby-asure commentedon Sep 4, 2026
Follow-up: tested switching the shadow-casting element from a
Gridto aBorderwith a solid, opaque, no-stroke background (per the discussion above and #26789) on the same affected Samsung Android 13 device. It did not resolve the issue — the shadow still renders as a flat, hard-edged band. Additionally, testing against a background that already has a light color tint nearby (not just plain white) made no visible difference either — the band looks equally solid/opaque either way, which suggestsOpacitymay not be respected at all on this device path, not just blur/Radius. Wanted to correct my earlier comment before it misleads anyone into thinking theBorderworkaround is reliable — for us it wasn't.