After upgrading "Microsoft.Toolkit.Uwp.UI.Lottie 6.0.0", using "Windows App Cert Kit" general metadata correctness verification failed #214

KevinZjYang · 2019-12-24T05:36:53Z

Describe the bug

This problem occurs whenever I upgrade "Microsoft.Toolkit.Uwp.UI.Lottie" to version 6.0.0. Downgrading to version 5.1.1 is all right.
See the error for details：#2882，Just like what @dpaulino said.
Because that issue has been closed.

XAML:

 <Border Background="Transparent"
               Visibility="{x:Bind IsLoading, Mode=OneWay}">
         <winui:AnimatedVisualPlayer>
                 <lottie:LottieVisualSource UriSource="ms-appx:///AnimatedVisuals/wave-loading.json" />
         </winui:AnimatedVisualPlayer>
 </Border>

[ X] Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
Microsoft.Toolkit.Uwp.UI.Lottie 5.1.1 work.

Steps to Reproduce

Steps to reproduce the behavior:

Upgrade "Microsoft.Toolkit.Uwp.UI.Lottie" to version 6.0.0
Create application package.
Test with Windows App Cert Kit.
See error

Expected behavior

 <TEST INDEX="58" NAME="一般元数据正确性" DESCRIPTION="元数据文件必须满足各种要求才是有效且正确的。" EXECUTIONTIME="00h:00m:09s.58ms" OPTIONAL="FALSE">
        <MESSAGES>
          <MESSAGE TEXT="文件 C:\Program Files\WindowsApps\8541KevinYang.28001B9000CE5_3.3.2.0_x64__z7y9f6aw0qfg2\Microsoft.Toolkit.Uwp.UI.Lottie.winmd 中类型为 Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass 的方法 add_AnimatedVisualInvalidated 的参数 value 引用了非 Windows 运行时类型 Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource。Windows 运行时类型仅可引用 Windows 运行时类型。" />
          <MESSAGE TEXT="未找到文件 C:\Program Files\WindowsApps\8541KevinYang.28001B9000CE5_3.3.2.0_x64__z7y9f6aw0qfg2\Microsoft.Toolkit.Uwp.UI.Lottie.winmd 中由类型 Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass 引用的类型 Microsoft.UI.Xaml.Controls.IAnimatedVisual。元数据文件中引用的所有类型都必须是可检测到的。" />
          <MESSAGE TEXT="文件 C:\Program Files\WindowsApps\8541KevinYang.28001B9000CE5_3.3.2.0_x64__z7y9f6aw0qfg2\Microsoft.Toolkit.Uwp.UI.Lottie.winmd 中类型为 Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource 的方法 add_AnimatedVisualInvalidated 的参数 value 引用了非 Windows 运行时类型 Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource。Windows 运行时类型仅可引用 Windows 运行时类型。" />
          <MESSAGE TEXT="未找到文件 C:\Program Files\WindowsApps\8541KevinYang.28001B9000CE5_3.3.2.0_x64__z7y9f6aw0qfg2\Microsoft.Toolkit.Uwp.UI.Lottie.winmd 中由类型 Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource 引用的类型 Microsoft.UI.Xaml.Controls.IAnimatedVisual。元数据文件中引用的所有类型都必须是可检测到的。" />
        </MESSAGES>
        <RESULT><![CDATA[FAIL]]></RESULT>
      </TEST>

Screenshots

Environment

NuGet Package(s): 
Microsoft.UI.Xaml 2.3.191211002
Microsoft.Toolkit.Uwp.UI.Lottie 6.0.0

Package Version(s): 

Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [x] May 2019 Update (18362)
- [ ] Insider Build (build number: )

App min and target version:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [x ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [ ] Insider Build (xxxxx)

Device form factor:
- [x] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT

Visual Studio 
- [ ] 2017 (version: )
- [x ] 2019 (version: ) 
- [ ] 2019 Preview (version: )

The text was updated successfully, but these errors were encountered:

ghost · 2020-01-08T06:00:26Z

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.

KevinZjYang · 2020-01-15T01:49:35Z

Can anyone help me?

michael-hawker · 2020-01-15T22:01:16Z

FYI @simeoncran

KevinZjYang · 2020-02-18T06:21:49Z

So long unsolved,I finally decided to deprecate "Microsoft.Toolkit.Uwp.UI.Lottie".
Use "Lottie Viewer" to convert json to c # code. Use as follows.

<winui:AnimatedVisualPlayer Width="200"  Height="160">
                    <animatedvisuals:WaveLoading />
</winui:AnimatedVisualPlayer>```

simeoncran · 2020-05-28T17:14:38Z

@KevinZjYang sorry to see that this wasn't given attention back in January. Did you ever try submitting despite the WACK error? We've noticed that the WACK can give false positives that the store doesn't care about.

jeremiethibeault · 2020-06-18T19:20:18Z

I'm having the same issue on my last store submission:
Target: 10.0.18362.0
Microsoft.Toolkit.Uwp.UI: 6.0.0
Microsoft.Toolkit.Uwp.UI.Lottie: 6.0.0

Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.

MatFillion · 2020-06-18T19:46:57Z

@simeoncran the above post from @jeremiethibeault failed at the store submission, so it's not a false positive :/

Full code is available here https://github.com/unoplatform/uno.ch9

simeoncran · 2020-06-18T23:08:46Z

Thanks @MatFillion and @jeremiethibeault. We are looking into this and will report back here.

simeoncran · 2020-06-19T18:39:14Z

@MatFillion and @jeremiethibeault. I'm told that there are known issues with how VS2017 packaged NuGet metadata that would explain what you're seeing.

Can you upgrade to the latest VS2019?

jeremiethibeault · 2020-06-19T20:03:37Z

Hey @simeoncran, I'm using VS2019 16.5.1. Not sure if the issue should still be applicable on this version. I can try on the latest version to see if it fixes the issue. Let me know if there is anything else I can try. I will also check the local WACK test result if I see the same error message, would be easier to debug that.

Thanks!

simeoncran · 2020-06-19T21:26:21Z

16.6.2 is the latest version. When I loaded your solution VS required that it first upgrade the projects. I wonder if that's a hint.

jeremiethibeault · 2020-06-22T12:46:48Z

I was able to reproduce the issue locally on VS 16.6.2

I simply created the app bundles using the built-in publish feature of VS for UWP then I ran the WACK test locally which gave me the same result as on the store.

FAILED
General metadata correctness
Error Found: The general metadata correctness test detected the following errors:
Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file C:\Program Files\WindowsApps\nventive.Ch9_1.0.6.0_x64__jc868da5z7jr4\Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file C:\Program Files\WindowsApps\nventive.Ch9_1.0.6.0_x64__jc868da5z7jr4\Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.
Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file C:\Program Files\WindowsApps\nventive.Ch9_1.0.6.0_x64__jc868da5z7jr4\Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file C:\Program Files\WindowsApps\nventive.Ch9_1.0.6.0_x64__jc868da5z7jr4\Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.
Impact if not fixed: Microsoft store doesn't allow apps that don't pass Windows Runtime Metadata Validation.
How to fix: Please ensure that the compiler you are using to generate your Windows Runtime types is up to date with with the Windows Runtime specifications.

These are the specs

App Architecture:
x64
Kit Version:
10.0.19041.1
OS Version:
Microsoft Windows 10 Pro (10.0.19041.0)

simeoncran · 2020-06-22T15:37:14Z

We have a local repro now. I still don't understand what is triggering it, but we're tracking down the experts and will keep this thread updated.

simeoncran · 2020-06-23T20:33:04Z

The issue is caused by the build not including Microsoft.UI.Xaml.winmd in the app package. You can check that by looking at the winmd files that get packaged into your .msix. As a result WACK doesn't find the references to IAnimatedVisualPlayer and IDynamicAnimatedVisualPlayer. We are looking into why that's happening.

EDIT: actually, the winmd is only missing from the sideload (MSIXBUNDLE) builds. The store builds (MSIXUPLOAD) have the MIcrosoft.UI.Xaml.winmd files. Usually you'd submit the MSIXUPLOAD files, but there are some circumstances where MSIXBUNDLE are needed in the store (has to do with corporate signing or something). @jeremiethibeault are you building MSIXBUNDLE (sideloading) or MSIXUPLOAD (store uploading) files?

jeremiethibeault · 2020-06-25T11:42:14Z

@simeoncran That's interesting, I'm building MSIXUPLOAD files through Visual Studio > Publish > Create app packages (the app is associated to the Microsoft Store)

The package I've submitted to the store is the MSIXUPLOAD one.

jeremiethibeault · 2020-06-25T12:33:39Z

I confirmed that the Microsoft.UI.Xaml.winmd file is inside .msixupload > .msixbundle > x64.msix > WinMetadata

simeoncran · 2020-06-25T14:08:59Z

Thank you, that's very helpful. Will keep you informed.

ajbennet · 2020-07-02T17:04:38Z

Hi @jeremiethibeault, this issue is taking longer than expected. I don't want you to be blocked till we figure this out, so I had asked for an exception to this rule for your app (Uno Ch9) and the exception is in place now. Please try submitting the package and let us know if you re able to do so. I ll keep you posted as we make progress in the actual issue. Thank you for your patience.

jeremiethibeault · 2020-07-07T14:17:12Z

Hey thanks @ajbennet, I submitted the app without the Lottie animation for now but I will take a look at resubmitting it with it.

Have a good day

BenJKuhn · 2020-07-14T00:38:08Z

We've been investigating this issue. The root cause appears to be an issue in the certification tests. There's a mismatch between how the tools bundle metadata in store submission packages and how the tests search for that data, specifically in the case where metadata is provided by framework packages. I'm glad @ajbennet was able to provide a workaround while we determine how to fix this issue.

matthewacme · 2020-07-15T20:17:35Z

It's still happening BTW
@ajbennet So how does one go about getting added to that list of app's that are excepted from this rule?

simeoncran · 2020-07-20T18:01:44Z

@matthewacme - can you give me some details and I'll see what I can do. No promises because I'm not really involved in the solution, but I can at least try to get your issue solved before this gets fixed for everyone.

under3415 · 2020-09-27T01:17:55Z

Hi everyone,

Thank you for your patience as we investigated the issue. A solution is in the works for subsequent versions of WinUI (2.5 and later) but as a workaround you can do the following for now:

Open the .csproj or .vcxproj file that has a reference to the Lottie NuGet package and insert this target at the bottom of the file right before :
<Target Name="_AddXamlWinmdToPackageLayoutRoot" AfterTargets="_CreatePackageLayout">
    <Copy
        SourceFiles="@(_PackageLayoutFileSource)"
        DestinationFiles="@(_PackageLayoutFileSource->'$(AppxLayoutDir)%(Filename)%(Extension)')"
        Condition="'%(Filename)%(Extension)' == 'Microsoft.UI.Xaml.winmd'" />
</Target>

Thanks!

I can also confirm that using Microsft.UI.Xams version 2.5.0-prerelease.200812001 also fixed the issue.

mentorfloat · 2020-10-05T09:34:03Z

@nishitha-burman , I am using XAML Island with a WPF App. I've added the <Target> at the bottom of my UWP .csproj right before </Project> but still failed the Windows Runtime Metadata Validation in a local WACK test.

Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.
Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.

I cannot try the 2.5.0-prerelease suggested by @under3415 because it will create 17 other Build errors in my case. An example from the 17 errors:
Payload file '...\WPF Base\bin\x86\Release\netcoreapp3.1\win-x86\Microsoft.UI.Xaml\DensityStyles\Compact.xaml' does not exist. from Line 3036 in ...\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets

If I use the following NuGet packages, it will build but fail the metadata test as mentioned above:
Microsoft.UI.Xaml 2.4.3
Microsoft.Toolkit.Uwp.UI.Lottie 6.1.2
Microsoft.Toolkit.Win32.UI.XamlApplication 6.1.2
Microsoft.Toolkit.Wpf.UI.XamlHost 6.1.2

nishitha-burman · 2020-12-08T00:13:42Z

@mentorfloat apologies for the delayed reply, were you able to resolve the issue?

mentorfloat · 2020-12-08T23:00:44Z

No, I ended up removing Lottie entirely and instead created custom UserControl containing Key-Frame Animations.

under3415 · 2020-12-08T23:25:06Z

The issue was resolved in Microsoft.UI.XAML 2.5.0-prerelease.201202003, but has re-appeared in stable release v2.5.0 :-(

nishitha-burman · 2020-12-09T20:34:26Z

Hi @under3415,

Does this issue appear in stable release v2.5.0 even with the workaround?

under3415 · 2020-12-09T21:44:26Z

Hi @under3415,

Does this issue appear in stable release v2.5.0 even with the workaround?

Hi
Yes that is correct.

It was working fine in pre-release without a workaround.
Since updating to v.2.5.0 it is rejected from the store even with the workaround in place.

Regards
Dejan

michael-hawker · 2020-12-09T22:51:23Z

@under3415 the WinUI pre-release and the release packages are built differently. FYT @ranjeshj

under3415 · 2020-12-09T23:02:58Z

If things are done differently for production release, doesn't that defy the purpose of pre-release testing?
D

nishitha-burman · 2021-03-12T20:43:05Z

If you hit this issue while trying to publish your app please raise a support ticket on the store while we look into this issue. You can raise a ticket by doing the following:

Open a web browser to http://aka.ms/storesupport
Click "Contact Us"
Select "Dashboard - Store apps and games, Hardware, Collaborative"

Thank you!

WACK expects to be able to find WinMDs for type resolution purposes in the root of the AppX, but when WinUI 2 is referenced via framework package, the WinMD is instead placed in a WinMetadata subdirectory. As a result, applications that reference nuget packages with references to WinUI 2, WACK certification fails. I'm not sure whether placing the WinMD file in that directory is still needed, so to work around this issue in the safest manner, this adds an additional build target that places the WinMD where WACK certification needs it to be. An example of an issue that will be resolved by this fix: CommunityToolkit/Lottie-Windows#214

nishitha-burman · 2021-03-16T16:22:41Z

Fix is checked into the WinUI 2 repo, should be fixed in 2.6.

rajeshangappan · 2021-04-12T10:34:31Z

After ugrading to latest version facing the below issue.
Exception thrown at 0x761EA8B2 :Microsoft C++ exception: winrt::hresult_error at memory location 0x09D3E9F8.

nishitha-burman · 2021-04-12T17:54:25Z

Hi @rajeshangappan,

Thank you for reaching out. Which version of WinUI and Lottie are you using?

under3415 · 2021-04-13T22:14:41Z

Hi
This is again an issue with the latest versions of UI XAML and Lottie:

Microsoft.UI.XAML 2.6.0-prerelease.210405001
Microsoft.Toolkit.Uwp.UI.Lottie v7.0.2

    Error Found: The general metadata correctness test detected the following errors:

    Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
    The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.ILottieVisualSourceClass in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.
    Parameter value of method add_AnimatedVisualInvalidated of type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd references the non-Windows Runtime type Microsoft.UI.Xaml.Controls.IDynamicAnimatedVisualSource. Windows Runtime types can reference only Windows Runtime types.
    The type Microsoft.UI.Xaml.Controls.IAnimatedVisual referenced by type Microsoft.Toolkit.Uwp.UI.Lottie.LottieVisualSource in file Microsoft.Toolkit.Uwp.UI.Lottie.winmd was not found. All types referenced in metadata files must be discoverable.

nishitha-burman · 2021-04-13T22:18:08Z

Hi @under3415, are you getting the same exception mentioned here #214 (comment) when using the latest versions of WinUI and Lottie?

under3415 · 2021-04-13T22:20:33Z

No, I am getting "metadata correctness test" error. I thought this bug is about that...

nishitha-burman · 2021-04-13T22:25:44Z

Yes both #405 and this issue are about the metadata correctness test. I was curious if you were also getting the issue mentioned here: #214 (comment). Thanks for the clarification!

We are looking into the metadata correctness test failure.

under3415 · 2021-04-13T22:28:40Z

I have also logged with with WinUI.

Do you understand what is going on here? The issue is fixed in one version, then regresses in the next!? It's happened twice already! It's really weird...

eliezerpMS · 2021-04-14T00:38:19Z

@under3415. Sorry to hear that you are hitting this issue again. Looking at your post here it looks like WACK was failing when you updated to Microsoft.UI.XAML 2.6.0-prerelease.210315002. When this happened what version of Lottie were you on? If you keep Lottie on the last version that passed WACK(please let us know which one that is) are you able to identify which versions of Microsoft.UI.XAML 2.6.0-prerelease caused you to fail WACK?

Does the issue repro for you with the Lottie Sample app when using Microsoft.UI.XAML 2.6.0-prerelease.210405001 and Microsoft.Toolkit.Uwp.UI.Lottie v7.0.2. If not do you have a simple app you could share with us that repros this issue with these versions of Lottie and Microsoft.UI.XAML?

under3415 · 2021-04-14T00:49:22Z

Lottie version does not seem to matter, the issue is fixed and broken in WinUI:

2.5.0-prerelease.201202003 OK
2.5.0 Broken
2.6.0-prerelease.210227001 OK
2.6.0-prerelease.210405001 Broken

I'm raising it here as well as in WinUI as I am not sure who needs to fix this, and why is it regressing.

under3415 · 2021-04-14T01:52:09Z

This issue only happens when you try to submit to Microsoft Store on a "Non-flighted submission".
It passes certification using the certification app and even the test flight in the store.

So to replicate the issue, create an app using lottie and winui and submit to store as "Non-flighted submission".

rajeshangappan · 2021-04-15T17:25:36Z

Hi @rajeshangappan,

Thank you for reaching out. Which version of WinUI and Lottie are you using?

Lottie version:7.0.2, Microsoft.UI.Xaml:2.5.0

nishitha-burman · 2021-07-02T15:36:55Z

Fixed by Microsoft.UI.XAML: microsoft/microsoft-ui-xaml#3780

michael-hawker transferred this issue from CommunityToolkit/WindowsCommunityToolkit Jan 15, 2020

simeoncran modified the milestone: 6.0 Jan 16, 2020

simeoncran closed this as completed May 28, 2020

simeoncran reopened this Jun 18, 2020

simeoncran assigned ajbennet Jun 19, 2020

ajbennet mentioned this issue Jun 22, 2020

App Submission to store & WACK Fails when using Lottie. #258

Closed

vincentcastagna mentioned this issue Jul 16, 2020

Re-added lottie for uwp unoplatform/Uno.Ch9#72

Merged

7 tasks

nishitha-burman reopened this Dec 7, 2020

nishitha-burman mentioned this issue Dec 8, 2020

Windows Store App Certification Fails after upgrading Microsoft.UI.XAML to v2.5.0 #405

Closed

llongley mentioned this issue Feb 17, 2021

Fix WACK certification error for transitive WinUI references microsoft/microsoft-ui-xaml#4218

Merged

nishitha-burman closed this as completed Mar 16, 2021

nishitha-burman reopened this Apr 12, 2021

nishitha-burman closed this as completed Jul 2, 2021

After upgrading "Microsoft.Toolkit.Uwp.UI.Lottie 6.0.0", using "Windows App Cert Kit" general metadata correctness verification failed #214

After upgrading "Microsoft.Toolkit.Uwp.UI.Lottie 6.0.0", using "Windows App Cert Kit" general metadata correctness verification failed #214

Comments

KevinZjYang commented Dec 24, 2019 • edited by michael-hawker Loading

Describe the bug

Steps to Reproduce

Expected behavior

Screenshots

Environment

ghost commented Jan 8, 2020

KevinZjYang commented Jan 15, 2020

michael-hawker commented Jan 15, 2020

KevinZjYang commented Feb 18, 2020 • edited Loading

simeoncran commented May 28, 2020

jeremiethibeault commented Jun 18, 2020

MatFillion commented Jun 18, 2020

simeoncran commented Jun 18, 2020

simeoncran commented Jun 19, 2020

jeremiethibeault commented Jun 19, 2020

simeoncran commented Jun 19, 2020

jeremiethibeault commented Jun 22, 2020 • edited Loading

simeoncran commented Jun 22, 2020

simeoncran commented Jun 23, 2020 • edited Loading

jeremiethibeault commented Jun 25, 2020

jeremiethibeault commented Jun 25, 2020

simeoncran commented Jun 25, 2020

ajbennet commented Jul 2, 2020

jeremiethibeault commented Jul 7, 2020

BenJKuhn commented Jul 14, 2020

matthewacme commented Jul 15, 2020 • edited Loading

simeoncran commented Jul 20, 2020

under3415 commented Sep 27, 2020

mentorfloat commented Oct 5, 2020

nishitha-burman commented Dec 8, 2020

mentorfloat commented Dec 8, 2020

under3415 commented Dec 8, 2020

nishitha-burman commented Dec 9, 2020

under3415 commented Dec 9, 2020

michael-hawker commented Dec 9, 2020

under3415 commented Dec 9, 2020

nishitha-burman commented Mar 12, 2021

nishitha-burman commented Mar 16, 2021

rajeshangappan commented Apr 12, 2021

nishitha-burman commented Apr 12, 2021 • edited Loading

under3415 commented Apr 13, 2021

nishitha-burman commented Apr 13, 2021 • edited Loading

under3415 commented Apr 13, 2021

nishitha-burman commented Apr 13, 2021 • edited Loading

under3415 commented Apr 13, 2021

eliezerpMS commented Apr 14, 2021

under3415 commented Apr 14, 2021

under3415 commented Apr 14, 2021

rajeshangappan commented Apr 15, 2021

nishitha-burman commented Jul 2, 2021

KevinZjYang commented Dec 24, 2019 •

edited by michael-hawker

Loading

KevinZjYang commented Feb 18, 2020 •

edited

Loading

jeremiethibeault commented Jun 22, 2020 •

edited

Loading

simeoncran commented Jun 23, 2020 •

edited

Loading

matthewacme commented Jul 15, 2020 •

edited

Loading

nishitha-burman commented Apr 12, 2021 •

edited

Loading

nishitha-burman commented Apr 13, 2021 •

edited

Loading

nishitha-burman commented Apr 13, 2021 •

edited

Loading