Sebastien Pouliot

Trying to decompile one of the methods shows ```csharp private void MoveNext() { //IL_004d: Unknown result type (might be due to invalid IL or missing references) //IL_0052: Unknown result type...

Nope, that did not help :|

I'm on a Mac computer. Is there Windows (or Mac) specific code paths for PDB ? Anyway I'll be trying your fix once pushed, thanks for looking :)

It works for me when using the Avalonia version of ILSpy (version 7.2.0.0.rc) on the Mac. So I could be an issue (only) with `ilspycmd`. Or there's something broken in...

In my original report I used the prebuilt tools (`ilspycmd` and ILSpy/Avalonia). This time I * Updated ILSpy repo to f2da2552001b1a77499f6821b6a7ce784aff416e (current HEAD) and ensure I had no local diff...

That makes sense. Thanks for the help! Sadly ILSpy/Avalonia does not show the metadata tables :( but I can check that with some code... or UPS will finally deliver me...

So after doing a (more proper) `./ilspycmd -genpdb tmp/Microsoft.iOS.dll -usepdb` I have no error (as expected) but don't get any document (0x30) from the assembly... binaries attached [Microsoft.iOS.zip](https://github.com/icsharpcode/ILSpy/files/9921409/Microsoft.iOS.zip)

I see them on Windows too. I noticed the workload number changed so I might have copied the pdb to the older location... I'll restart this from scratch and compare...

Is that something that can be reproduced with the MT.D sample app ? Also does this happens on the simulator, devices (I assume so, since it's Ad-Hoc) or both ?...

@rolfbjarne I can duplicate this with `dotnet new ios` and VSfM. I used `net6.0-ios` since it's LTS. I just put a breakpoint on the first line, start debugging on my...