| There's no interpreter when using NativeAOT, and as such the `UseInterpreter` |
| and `MtouchInterpreter` properties have no effect. |
| NativeAOT requires trimming, and `MAUI` isn't trimmer-safe, and thus |
| unfortunately `MAUI` projects don't typically work with NativeAOT (we hope to |
| rectify this situation for .NET 9). |
| There are no known issues specific to our platforms with NativeAOT; but the |
| [limitations][2] are exactly the same as for other platforms. |
| There are no known issues specific to our platforms with NativeAOT; but the |
| [limitations][2] are exactly the same as for other supported platforms. |
| Nevertheless, we would like to point out a few features that are not available with NativeAOT, that are with Mono, when targeting Apple platforms: |
| - NativeAOT does not support managed debugging. |
| - There's no interpreter when using NativeAOT, and as such the `UseInterpreter` |
| and `MtouchInterpreter` properties have no effect. |
| - NativeAOT requires trimming, and `MAUI` isn't trimmer-safe, and thus |
| unfortunately `MAUI` projects don't typically work with NativeAOT (we hope to |
| rectify this situation for .NET 9). |