.NET MAUI: Disable dark mode support

To disable dark mode support in .NET MAUI, you need to use these code snippets in each platform

Android

In the MainApplication add the following line:

public MainApplication(IntPtr handle, JniHandleOwnership ownership) : base(handle, ownership)
{
     AppCompatDelegate.DefaultNightMode = AppCompatDelegate.ModeNightNo;
}

iOS

In the info.plist file, add the following keyvaluepair:

    <key>UIUserInterfaceStyle</key>
    <string>Light</string>

WinUI

In the App.xaml.cs (the windows version one) add the following line:

public App()
	{
		this.InitializeComponent();
        RequestedTheme = ApplicationTheme.Light;
	}

.NET MAUI iOS – Can’t launch the app, crashes on splash screen error

If you are facing issues launching your iOS application in VS Code, then try to analyse the Debug Console of your application.
If you see things like this:

Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/Newtonsoft.Json.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/System.Reflection.Emit.Lightweight.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/System.Reflection.Emit.ILGeneration.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/System.Reflection.Primitives.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/System.Data.Common.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/Syncfusion.Maui.Inputs.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/ZF.Packages.Maui.Fonts.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/ZF.Packages.Maui.Views.Alerts.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/Refit.HttpClientFactory.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/Microsoft.Extensions.Http.dll
Loaded assembly: /private/var/containers/Bundle/Application/50529075-A03E-45EC-99F6-0A539036E226/app.app/MetroLog.Maui.dll

And then your application suddenly crashes showing the splashscreen, then the debugger might be slow.

XCode 15 have problems with debugging. If you have “Connect via network” enabled on your XCode settings under Devices and Simulators, than this might be the problem. Even if you are connecting your phone wired, it starts the application debugging via wifi.
Try updating XCode to 15.4, and update your OS to macOS Sonoma 15.4 aswell

You can countercheck this problem by disabling the wifi on your physical device. In this case the app installs, but crashes instantly when trying to launch it.

Additionally in Visual Studio code the solution you can disable some settings in the C# extension’s settings the Debug > Logging to speed up the loading progress when launching your app.

Publishing .NET MAUI Apps with VS Code

In this tutorial, I will guide you through the step-by-step process of publishing .NET MAUI apps using Visual Studio Code and the ‘.NET MAUI – Archive / Publish tool’ extension by me. This extension simplifies the publishing process by providing a user-friendly interface within VS Code.

Without the help of an extension

You will need to dive into a terminal, and give out the following commands, based on which platform you want to build for.

# Android:
dotnet publish -f net8.0-android -c Release -p:AndroidKeyStore=true -p:AndroidSigningKeyStore={filename}.keystore -p:AndroidSigningKeyAlias={keyname} -p:AndroidSigningKeyPass={password} -p:AndroidSigningStorePass={password}
# iOS:
dotnet publish -f net8.0-ios -c Release -p:ArchiveOnBuild=true -p:RuntimeIdentifier=ios-arm64 -p:CodesignKey="Apple Distribution: John Smith (AY2GDE9QM7)" -p:CodesignProvision="MyMauiApp"

You can learn more, how to do it without my extension at:
https://learn.microsoft.com/en-us/dotnet/maui/ios/deployment/publish-cli?view=net-maui-8.0
and
https://learn.microsoft.com/en-us/dotnet/maui/android/deployment/publish-cli?view=net-maui-8.0

But don’t waste your time. I’ve put together a Visual Studio Code extension for you that will easily save you those unnecessary lines and allow you to publish from the UI.

Step 1: Install VS Code Extension


Visit the VS Code Marketplace and install the ‘.NET MAUI – Archive / Publish tool’ extension by ‘banditoth’.

You might be required to reload your VS Code instance.

Step 2: Open Your .NET MAUI Project

Launch Visual Studio Code and open your .NET MAUI project.

Step 3: Access the Command Palette

Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac) to open the command palette in Visual Studio Code.

Step 4: Choose Publish Android or Publish iOS

Type ‘MAUI Publish’ in the command palette. You will see two options: ‘MAUI: Publish Android’ and ‘MAUI: Publish iOS’. Select the one that corresponds to your target platform.

Publishing for Android:

The extension will prompt you to choose between a signed or non-signed binary. Select your preferred option.

Next, choose the package format – either apk (Android Package) or aab (Android App Bundle).

If signing is required (for a signed binary), the extension will list all installed keystore files. Choose the appropriate keystore.

Enter the keystore password when prompted.

The extension will start the publishing process, and you’ll see progress information directly in the VS Code output.

Publishing for iOS:

Select ‘MAUI: Publish iOS’ from the command palette.

The extension will ask for the code signing identity. Choose the desired code signing identity from the available options.

Next, choose a provisioning profile to sign the app.

The extension will initiate the publishing process for iOS, displaying progress information in the VS Code output.

Conclusion

With the ‘.NET MAUI – Archive / Publish tool’ extension, publishing your .NET MAUI apps for Android and iOS becomes a straightforward process within Visual Studio Code. You no longer need to manually execute complex CLI commands; instead, you can leverage the extension’s user-friendly interface for a seamless publishing experience. Enjoy the convenience and efficiency of this simplified workflow for your .NET MAUI projects!

Support the project

You can find more information about how to contribute on this project at the project’s github page: https://github.com/banditoth/maui-archiver-vscode

.NET MAUI iOS – Azure Pipelines error: ‘x’ is not available in iOS 16

The Error: The error message suggests that the ‘UIKit.UISceneSessionActivationRequest’ type, used as a parameter in ‘UIKit.UIApplication.ActivateSceneSession,’ is not available in iOS 16.2 and was introduced in iOS 17.0. This discrepancy indicates a version misalignment in the development environment, specifically with the iOS SDK and Xcode.

Root cause

The root cause of this error lies in the version of the macOS image used in the Azure Pipelines configuration. By default, the ‘macOS-latest’ image is pulled, which corresponds to macOS 12 (at the time of the blog post). However, the .NET MAUI app with Azure Pipelines requires macOS v13 to work seamlessly, as it aligns with the necessary dependencies for iOS development.

Resolution

To resolve this error, developers need to update the macOS image specified in the Azure Pipelines configuration. Instead of using ‘macOS-latest,’ the configuration should be modified to use ‘macOS-13.’ This ensures that the appropriate version of macOS is utilized during the build process, addressing the compatibility issues with iOS 16.2 and the required UIKit types.

Step-by-Step

-Open your Azure Pipelines configuration file (typically named azure-pipelines.yml).
-Locate the section where the macOS image is specified. It might look something like this:

pool:
  vmImage: 'macOS-latest'

-Update the image reference to ‘macOS-13’:

pool:
  vmImage: 'macOS-13'

-Save the changes to the configuration file.
-Commit the updated configuration file to your version control system (e.g., Git).
-Trigger a new build in Azure Pipelines, and the updated macOS image will be used.

.NET MAUI + Visual Studio Code: Debugging Cancelled: XCode Not Found

One common issue users face is the “Debugging Cancelled: XCode Not Found” error on macOS. In this blog post, we’ll explore a step-by-step guide to troubleshoot and resolve this vexing problem.

Solution 1: Verify VS Code Command Line Tools Installation
Before diving into complex solutions, let’s start with the basics. Ensure that the VS Code command line tools are correctly installed on your machine. Run the following command in the terminal:

xcode-select --install

This command installs the necessary tools for XCode. After installation, verify that the path is correctly set by running:

xcode-select -p

Ensure that the path points to your XCode installation. If not, set it using the following command:

sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

Solution 2: Force Quit and Relaunch VS Code
Sometimes, issues can be resolved by simply force quitting VS Code and relaunching it. This action ensures a fresh start, eliminating any temporary glitches that might be causing the problem.

Solution 3: Restart VS Code
A restart can work wonders in resolving software-related issues. Save your work, close VS Code, and then relaunch it. This simple step can refresh the IDE and might solve the “Debugging Cancelled: XCode Not Found” issue.

Solution 4: Reinstall .NET MAUI Extension
If the problem persists, the next step is to reinstall the .NET MAUI extension. Extensions can occasionally become corrupted or outdated, leading to compatibility issues. Open the Extensions view in VS Code, locate the .NET MAUI extension, and uninstall it. Afterward, reinstall the latest version from the Visual Studio Code marketplace.

Solution 5: Reinstall Visual Studio Code
If all else fails, consider reinstalling Visual Studio Code. Uninstall the current version, download the latest version from the official website, and perform a clean installation. This ensures that any corrupted files or configurations are completely removed, and you start with a fresh setup.

This content has 8 months. Some of the information in this post may be out of date or no longer work. Please, read this page keeping its age in your mind.