-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Known Issues
You may encounter the following known issues in addition to verified issues. Each may include workarounds, mitigations, or expected resolution timeframes.
Related known issues:
When installing .NET MAUI on win-arm64 machines, you might get the error:
Workload ID maui isn't supported on this platform.
To work around this, manually patch the WorkloadManifest.json files as mentioned here.
On macOS, if you encounter a build error related to mono-aot-cross:
An error occurred trying to start process '/usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.maccatalyst-x64/8.0.0-preview.1.23115.2/Sdk/../tools/mono-aot-cross'. Permission denied
To work around the issue, by making the file executable:
chmod +x /usr/local/share/dotnet/packs/Microsoft.NETCore.App.Runtime.AOT.osx-x64.Cross.maccatalyst-x64/8.0.0-preview.1.23115.2/tools/mono-aot-crossThis is tracked in dotnet/runtime#82201.
Platform specifics are APIs built into .NET MAUI for exercising features specific to only one platform. Issue #5856 is tracking the known gaps compared to Xamarin.Forms including:
- Button
- UseDefaultPadding
- UseDefaultShadow
- NavigationPage
- BarHeight
- NavigationPage
- HideNavigationBarSeparator
- StatusBarTextColorMode
- Page
- UseSafeArea
- PrefersHomeIndicatorAutoHidden
- PrefersStatusBarHidden
- PreferredStatusBarUpdateAnimation
- VisualElement
- BlurEffect
- CanBecomeFirstResponder
- FlyoutPage
- CollapseStyle
- CollapsedPaneWidth
- Page
- ToolbarPlacement
- TabbedPage
- HeaderIconsEnabled
- WebView
- ExecutionMode
- IsJavaScriptAlertEnabled
Use handlers to exercise these APIs at the platform level. See Customize .NET MAUI controls with handlers and Invoke platform code.