Disabled Button Visual State doesn't Update Image Source

[mkehoe-Extron]

Description

When you change the state of a button to disabled, the visual state manager is not applying changes to the ImageSource.

This issue is on Android. Works as expected on Windows.

Issue exists on both latest dotnet 6 and dotnet 7 preview.

Steps to Reproduce

1. Launch the sample app.
2. Click the top button and it will set the bottom button state to disabled.
3. You will notice the text color change on the bottom button. The image source is supposed to change to as well, but it stays as the original color.

Link to public reproduction project repository

https://github.com/mkehoe-Extron/MauiAndroidButtonStateIssue

Version with bug

6.0.486 (current)

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

Android API 31

Did you find any workaround?

No response

Relevant log output

No response

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[jknaudt21]

Hey @samhouts and @jsuarezruiz I think this issue has already been solved. I tried reproing using the Sandbox project and everything worked fine. My guess is that this got fixed on this PR Javier sent in November: #11146. The breakpoints I added are hitting Javier's code, plus the PR was sent after this issue was reported. Things seem to be working fine here :)

Can this issue be closed?

[samhouts]

Hey @samhouts and @jsuarezruiz I think this issue has already been solved. I tried reproing using the Sandbox project and everything worked fine. My guess is that this got fixed on this PR Javier sent in November: #11146. The breakpoints I added are hitting Javier's code, plus the PR was sent after this issue was reported. Things seem to be working fine here :)

Can this issue be closed?

Excellent! Let's add the s/try-latest-version label and see if anyone else is still experiencing the issue.

Thank you!!