-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue using dotnet trace
on MacCatalyst apps
#73715
Comments
Even with that alert (which I think just happens because the app can't talk to the API, you'd need to run a separate project for that) shouldn't tracing still work? It's just some code that runs. |
Yes, I see the "Oppss" on iOS and Android, but |
When running the trace command independently, some more interesting traces are found
|
that is interesting indeed, stepping through |
You're running into this: #71492 |
Thanks, the fix for that was backported to the pending 6.0.9 runtime release: #72002 There's also a workaround that you can use in the meantime: #71492 (comment) |
Description
I filed this here, as it seems related to Mono diagnostics.
This works for a MAUI project template:
dotnet new maui
dotnet build -c Release -f net6.0-maccatalyst -r maccatalyst-arm64
dotnet trace collect --format speedscope -- bin/Release/net6.0-maccatalyst/maccatalyst-arm64/MyApp.app/Contents/MacOS/MyApp
I get a
.nettrace
and.speedscope
that are valid.However, in both a customer's app and the .NET Podcast sample:
https://github.com/microsoft/dotnet-podcasts/tree/main/src/Mobile
The app attempts to launch, but shows the macOS "bouncy" animation. It appears the app is stuck and never launches. If I Ctrl+C
dotnet trace
writes a partial.nettrace
file that looks to be broken as if the app crashed.I'm not sure how to diagnose further, but I can try something, thanks!
Reproduction Steps
Try my steps above on the .NET Podcast sample:
https://github.com/microsoft/dotnet-podcasts/tree/main/src/Mobile
Expected behavior
I can use
dotnet trace
on the .NET Podcast app.Actual behavior
I can't seem to use
dotnet trace
on the .NET Podcast app.Regression?
I'm not sure if many have used
dotnet trace
on MacCatalyst, or if I'm the first.Known Workarounds
No response
Configuration
Running with .NET 6.0.400 on Apple M1, macOS 12.5 Monterey
Other information
No response
The text was updated successfully, but these errors were encountered: