Timo Partl

Results 202 comments of Timo Partl

@jamescrosswell you can reproduce this behavior / stack trace by simply throwing an exception in the `AppDelegate.FinishedLaunching` method in an NativeAot-compiled app. You might have to upload a build to...

> [@bitsandfoxes](https://github.com/bitsandfoxes) what do we want to do about this? Would it not be possible to allow an optional/temporary way to disable the changing of marshalling bahavior, [as I suggested...

I was able to run a Native AOT compiled app locally on a physical device using `dotnet publish /t:Run /p:_DeviceName=DEVICEID` where DEVICEID can be queried using `xcrun xctrace list devices`

Yes I didn't receive useful stack traces, because the app process crashed here when going through the native & managed layers: https://github.com/xamarin/xamarin-macios/blob/907081f787315704a01c940cf28b46b47db23df0/runtime/runtime.m#L2362-L2364 - at least this is the explanation I...

When I create a blank iOS app (`dotnet new ios`) and throw an exception in `FinishedLaunching` while running with NativeAot, I **do not** get this part in the native stack...

> I'm running `dotnet publish ./samples/Sentry.Samples.Maui/Sentry.Samples.Maui.csproj -t:Run -f net9.0-ios18.0 -r ios-arm64 /p:_DeviceName=00008030-00120D190A38802E` I used a similar command when testing, I think I didn't specify the -f and -r options, but...

I did a quick test with both 5.0.1 and 5.1.0 and throwing an exception in `FinishedLaunching` **5.0.1** ![Image](https://github.com/user-attachments/assets/1a42ed36-0d51-4400-8f9c-7885a2fe9e52) ![Image](https://github.com/user-attachments/assets/2b0b35bc-5513-4b7a-8b8b-a5ef6c886fd3) **5.1.0** ![Image](https://github.com/user-attachments/assets/ba2481b2-6fed-4285-9378-a4ec6b962b85) So with 5.1.0 I seem to get two crash...

Yes, the original issue indeed appears to be fixed

Just received another one of this error, in another app of mine. Same stack trace, also iOS 18. Will consider adding the `MtouchExtraArgs` if this turns out to happen more...

I haven't seen this crash anymore, perhaps it was fixed with the changes to `NSUrlSessionHandler` last year? I think this can be closed