InputTransparent="true" on a Layout breaks child controls on Android

[rudyspano]

Description

On Android, setting InputTransparent=true on a layout (for example: Grid) leads to bugs on child controls.
If we want to display after a user action a child control that was previously not visible (IsVisible=false => true), the first time the control is not displayed as you can see in my reproduction sample.
InputTransparentIssue.zip

inputtransparentbug.mov

I've also seen that animating other properties on child controls of a layout also causes weird behaviors.

Steps to Reproduce

No response

Link to public reproduction project repository

No response

Version with bug

8.0.21 SR4.1

Is this a regression from previous behavior?

Yes, this used to work in Xamarin.Forms

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Android: InputTransparent adversely affects position or visibility of Labels. (#15090), similarity score: 0.82
• [BUG] Grid is always InputTransparent (.NET MAUI 9.0 Preview 2) (#21553), similarity score: 0.80
• CascadeInputTransparent not working (#19332), similarity score: 0.80

Closed similar issues:

• under iOS, "parent.InputTransparent = false" does not propagate to children as it should (#10203), similarity score: 0.82
• InputTransparent property does not work on Android (#9069), similarity score: 0.81

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Zhanglirong-Winnie]

Verified this issue with Visual Studio 17.10 Preview 6.0 (8.0.21). Can repro on android platform with sample project.

[PureWeen]

I've also seen this occasionally with CV and controls that are inside a WrapperView