Expression animation does not work after update the Microsoft.Toolkit.Uwp.UI.Animations nuget package

[h82258652]

Describe the bug

After update the Microsoft.Toolkit.Uwp.UI.Animations nuget package. The expression animation does not work.

Regression

7.0.2

Reproducible in sample app?

• This bug can be reproduced in the sample app.

Steps to reproduce

I create a bug demo here: https://github.com/h82258652/ToolkitExpressionReferenceBugDemo
The 7.0.2 version is working and the 7.1.2 version is not working.

Expected behavior

The 7.1.2 version should work like the 7.0.2 version.

Screenshots

No response

Windows Build Number

• Windows 10 1809 (Build 17763)
• Windows 10 1903 (Build 18362)
• Windows 10 1909 (Build 18363)
• Windows 10 2004 (Build 19041)
• Windows 10 20H2 (Build 19042)
• Windows 10 21H1 (Build 19043)
• Windows 11 21H2 (Build 22000)
• Other (specify)

Other Windows Build number

No response

App minimum and target SDK version

• Windows 10, version 1809 (Build 17763)
• Windows 10, version 1903 (Build 18362)
• Windows 10, version 1909 (Build 18363)
• Windows 10, version 2004 (Build 19041)
• Other (specify)

Other SDK version

No response

Visual Studio Version

2022

Visual Studio Build Number

4.8.04161

Device form factor

Desktop

Nuget packages

7.0.2
7.1.2

Additional context

No response

Help us help you

No.

Hello h82258652, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.

[LalithaNadimpalli]

The link provided for the bug didn't work for me, Can you provide more info on the issue

[h82258652]

Oh, sorry. I forget to make it public. It should be works now. Could you try again? Thanks.

[Arlodotexe]

Thanks for supply the repro @h82258652.

After some investigation I managed to find the commit that introduced this issue: fa6a3ed.

I'll continue debugging this on Monday. @arcadiogarcia, this is code you added in #4183, any quick insights you can provide in the meantime?