Toolkit Sample App crashes after install when clicking on DataGrid control.

[Arebusf21]

When I install the sample app, select Controls from the menu, and then click on DataGrid, I can see the DataGrid page for an instance and then the app crashes. Uninstalling/Reinstalling does not seem to help.
I installed the app from the store.
Has anyone else experienced this and is this a known bug?

[michael-hawker]

Thanks @Arebusf21 can you provide some more details about what OS version you're on? We haven't seen this locally. Is it only the DataGrid sample that crashes for you?

[Arebusf21]

Hi: Thanks for the response, yes: so far it's only DataGrid. I am running Windows 10 Pro, Version 10.0.19042 Build 19042.
I am developing an App that uses DataGrid and have the control working fine in my dev environment.
I have been referring back to the Sample App & DataGrid quite frequently so its no coincidence that DataGrid should be my problem.
I have removed the Windows Community Sample App and then reinstalled it, I have tried a Reset and a Terminate to no avail.
Does the toolkit preserve settings across multiple installs? This is the only thing I can think off that could cause this on my end.

[michael-hawker]

We don't have any settings like that. We just store the history of samples you've opened to display on the home page recent list and a cache of documentation pulled down for offline usage later, but that's for every sample. DataGrid doesn't really do anything unique here.

Does the EventViewer show any error on the app crash that contains more info? What's your locale/region settings? Just wondering if we can figure out what may be different in your environment...

[Arebusf21]

Yes, there is an entry in the Event Viewer/Windows Logs/Application, here is an XML detail view:
``

• 1001 0 4 0 0 0x80000000000000 89509 Application ALSDESKTOP
• 1620092490822941631 5 MoAppCrash Not available 0 Microsoft.UWPCommunityToolkitSampleApp_7.1.0.0_x64__8wekyb3d8bbwe praid:App 0.0.0.0 614a37b4 combase.dll 10.0.19041.1202 474f0ba7 80131537 00000000000862a6 \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8F5B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.UWPCom_fc9edde7ea3f73c7d943bdd7fec7d686692b9980_23a8cc53_b2e9ffc5-b786-4f90-8a99-fd43b64f8474 0 73ba0996-1a29-41f5-b6ba-d19d96457389 268435456 7682c31d4b0b3dfe467bb9896ac77bbf 0

[Arebusf21]

Here is a more readable copy as an attachmen
wct_DataGrid_Error.txt
t:

[XAML-Knight]

Was not able to repro, with either the Sample App from the Store, or when debugging from Visual Studio (x64, Debug, 16.11.3, Windows 10 19042)

[Arebusf21]

I have downloaded the Windows Community Toolkit, all 52 projects and built them in my dev environment. I have made the Microsoft.Toolkit.Uwp.SampleApp the startup project and it builds and loads ok. There are a lot of warning messages around not being able to find Git.Targets.
I can run the app and everything looks fine until I try and look at the DataGrid which promptly crashes the app.
Here is a copy of the Build Output:
WCT_OutputWindow.txt
Could it be that I have the build folder nested too deep?
Here is a copy of an exception reported while in debug:
An exception of type 'System.FormatException' occurred in System.Private.CoreLib.dll but was not handled in user code
String '05/29/1953' was not recognized as a valid DateTime.
So, I noticed I had changed my date time formats, short date and long date to dd-mmm-yy and dddd, d MMMM, yyyy
Resetting them back to defaults removes the exception and now I can see the DataGrid.

[michael-hawker]

Thanks @Arebusf21 that's useful, seems like it may be coming from how we're parsing the data in the sample app file for the DataGrid example and picking up the current machine's culture than the culture the data is stored in.

If you turn on all the managed exceptions and turn off 'just my codce' it should certainly stop when that exception is hit in the project (or underlying json lib) and give you more details about a stack trace that can help us track down the specific call causing an issue.

I would suspect we're getting hit with an issue here:

WindowsCommunityToolkit/Microsoft.Toolkit.Uwp.SampleApp/Data/DataGridDataSource.cs

Line 51 in 84adf91

First_ascent = DateTimeOffset.Parse(values[7]),