Problem with Community Toolkit MediaElement

Lloyd Sheen 1,351

I am having trouble with the Community Toolkit MediaElement and cannot find a way to tell that team about the problem. The problem is simple in that I have a content page with 5 Content Views. I have buttons to show the view and when I run it thru the emulator and VS it works correctly. If I try to run it directly from the emulator it just stops and I have put lots of trace elements (my own) to trace what it going on hoping to capture the error but it is not showing an error.

How can I tell the Community Toolkit team about the problem?

Lloyd Sheen 1,351 Reputation points

2023-05-30T20:16:28.3633333+00:00

If I comment out the MedaElement then the app runs directly from the emulator.

1 answer

Rob Caplan - MSFT 5,412 Reputation points Microsoft Employee

2023-05-30T20:38:46.6933333+00:00

Quoting my answer to your post from three weeks ago: How do I get support for the Community Toolkit

You can find the MAUI Community Toolkit github repo at https://github.com/CommunityToolkit/Maui. This is also linked in the Community Toolkit documentation.

If you need help, you'll need to provide details on your environment and the specific problem: what code are you using and steps are you taking, what is the expected behaviour, and how is that different from the actual behaviour.
Please sign in to rate this answer.
Lloyd Sheen 1,351 Reputation points

2023-05-30T21:23:52.6533333+00:00

I can use github thru VS but when I go your link I could not sign in. Eventually it showed me a userid that I have never used that I know of. When I signed in with that userid I just got a 404 with the above link. I followed what I got to by searching for Maui Community Toolkit and it brought me to a page. I can find nothing on this page that shows how to report a problem but while testing the problem I found that it is very likely that the problem is not with the MediaElement but with VS and emulator.

I was commenting out all the elements of the ContentView and when I commented out a CollectionView the problem went away. I uncommented out the CollectionView and the problem reoccured. I then commented out the ItemTemplate and it showed the list with the object type as each line. When I uncommented out the ItemTemplate the error occured again.

It seems the problem was with a Style that was being used in the ItemTemplate. The StaticResource did not exist (problem copying from old version of the app). When I got rid of the style then all worked as it should.

Seems that the problem is that when running thru VS in debug mode it ignores the fact that the style does not exist. When attempting to run the app directly from the emulator (Android) then it stops when attempting to show the CollectionView. It seems that VS deals with the error (not finding the Style) and keeps on running, but when I run the app directly from the emulator it fails.

Lloyd Sheen 1,351 Reputation points

2023-05-30T21:36:34.6833333+00:00

Further information. I created a new Maui app using the standard template. I added a Style as follows:

If you test this it will work in debug mode with no error. Then with the emulator still open locate the app in the emulator and try to start it. I will immediately stop and provide no information as to why.

I know that the problem is solved by either creating the Style or removing the reference it from the XAML but in this case debugging it and running it cause two different things to happen. If you load it to a phone the same thing happens.

<Label Text="Hello, World!" SemanticProperties.HeadingLevel="Level1" Style="{StaticResource xxxx}" FontSize="32" HorizontalOptions="Center" />

Rob Caplan - MSFT 5,412 Reputation points Microsoft Employee

2023-06-01T22:14:41.5466667+00:00

Do you have a global exception handler that may be eating the XamlParseException or TargetInvocationException?

Adding your style to a generic wizard-based app, VS 17.7.0p1's debugger stops as expected for these errors in Maui 7.0 on both Windows and Android. VS's output window IDs the specific problem:

[mono-rt] ---> Microsoft.Maui.Controls.Xaml.XamlParseException: Position 15:17. StaticResource not found for key xxxx" output,

If you're not handling those exceptions and the app still runs past them then there's something sufficiently odd going on that you'll probably need to open a case if you want help tracking it down. If it's caused by a Microsoft bug then the case won't be charged.

--Rob

Lloyd Sheen 1,351 Reputation points

2023-06-01T22:21:59.0933333+00:00

I showed the error by using the Maui template with the click counter. Just putting the non existant style caused the error. For me if I execute on the Android emulator thru VS it runs with no error. If I scroll the emulator to show the apps on it and execute the sample app it just stops with no indication as to why. BTW I have never used a XAMLParseException.
Sign in to comment