You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
We've been recently looking for a universal tool which we can use in most of our projects focused arount the .NET tech stack.
I've tried to hook up the NewRelic to .NET Maui Blazor Hybrid App, but it apperas to only track app launches. Logs and crashes unfortunately are not properly sent to the new relic UI. I've tried it using .NET8 and .NET9.
On basic .NET8 MAUI everything seems to work (crashes are reported properly)
Is there a way to conifgure NewRelic to work on .NET Maui Blazor Hybrid App? I've followed the configuration tutorial from your github page (https://github.com/newrelic/newrelic-maui-plugin)
Steps to Reproduce
Create new .NET MAUI Blazor Hybrid App project
Install NewRelic.Maui.Plugin nuget package
Configure it following the instructions from the github page
Throw test exception after some button click
Expected Behavior
On NewRelic site there should be visible errors on the dashboard (but there is only shown app launch, so NewRelic does send some information).
Relevant Logs / Console output
On basic .NET MAUI project, NewRelic succesfully sends the crash information
As I previously mentioned, it works properly on .NET MAUI app (sending crashes and logs) but on .NET MAUI Blazor Hybrid App it only tracks app launches.
The text was updated successfully, but these errors were encountered:
@Qkyyy Did you try the New Relic browser agent for the Blazor app, which is basically built using JavaScript and HTML? Our Maui agent is mostly for Android and iOS agents, which are built using C#.
@Qkyyy Did you try the New Relic browser agent for the Blazor app, which is basically built using JavaScript and HTML? Our Maui agent is mostly for Android and iOS agents, which are built using C#.
Hey, thanks for the quick reply!
Although while this is working, I have a couple of questions.
NewRelic doesnt seem to gather crash informations when you throw exceptions from within the .razor pages. throw new Exception("please catch me"); and await JSRuntime.InvokeVoidAsync("throwJsException") are not properly caught. When I call this script from the index.html like this:
<script>
function throwJsException() {
throw new Error("This is a JavaScript exception v222");
}
throwJsException();
</script>
It does get caught almost instantly - but as I said, only when I call the function from index.html which is a big problem for Blazor.
Also, while using the browser app for .NET MAUI Blazor Hybrid App, caught exceptions doesnt seem to have crucial information about the device as in the .MAUI Agent. Is there something we could do to make this work for our case?
Description
Hello.
We've been recently looking for a universal tool which we can use in most of our projects focused arount the .NET tech stack.
I've tried to hook up the NewRelic to .NET Maui Blazor Hybrid App, but it apperas to only track app launches. Logs and crashes unfortunately are not properly sent to the new relic UI. I've tried it using .NET8 and .NET9.
On basic .NET8 MAUI everything seems to work (crashes are reported properly)
Is there a way to conifgure NewRelic to work on .NET Maui Blazor Hybrid App? I've followed the configuration tutorial from your github page (https://github.com/newrelic/newrelic-maui-plugin)
Steps to Reproduce
Expected Behavior
On NewRelic site there should be visible errors on the dashboard (but there is only shown app launch, so NewRelic does send some information).
Relevant Logs / Console output
On basic .NET MAUI project, NewRelic succesfully sends the crash information
newrelic CrashSender: Crash 7279094a-f035-4e15-810c-7d29fb8c45d5 successfully submitted.
Your Environment
.NET 8, .NET 9
NewRelic.Maui.Plugin 1.1.6
Additional context
As I previously mentioned, it works properly on .NET MAUI app (sending crashes and logs) but on .NET MAUI Blazor Hybrid App it only tracks app launches.
The text was updated successfully, but these errors were encountered: