Known Issues

.NET MAUI 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:

• .NET for iOS

Upcoming services release:

• 6.0.3xx-sr1
• 6.0.3xx-sr2

Some Platform Specifics are not available in .NET MAUI

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:

Android

• Button
  • UseDefaultPadding
  • UseDefaultShadow
• NavigationPage
  • BarHeight

iOS

• NavigationPage
  • HideNavigationBarSeparator
  • StatusBarTextColorMode
• Page
  • UseSafeArea
  • PrefersHomeIndicatorAutoHidden
  • PrefersStatusBarHidden
  • PreferredStatusBarUpdateAnimation
• VisualElement
  • BlurEffect
  • CanBecomeFirstResponder

Windows

• FlyoutPage
  • CollapseStyle
  • CollapsedPaneWidth
• Page
  • ToolbarPlacement
• TabbedPage
  • HeaderIconsEnabled
• WebView
  • ExecutionMode
  • IsJavaScriptAlertEnabled

Workaround

Use handlers to exercise these APIs at the platform level. See Customize .NET MAUI controls with handlers and Invoke platform code.

Maps control is unavailable

The Xamarin.Forms.Maps NuGet or an alternative control from .NET MAUI is not available in .NET 6.

Workaround

For platforms such as Android, iOS, and Mac Catalyst that provide maps controls, you can create a handler to surface those controls in .NET MAUI. See Customize .NET MAUI controls with handlers and Creating a .NET MAUI Maps Control blog post.

For platforms without a native control, you can use a web based map and host that within a WebView.