If you are facing issues on macOS, with the retiring Visual Studio for Mac launching your .NET MAUI app, or restoring the packages on it:
error NETSDK1139: The target platform identifier android was not recognized.
error NETSDK1139: The target platform identifier iOS was not recognized.
error NETSDK1139: The target platform identifier MacCatalyst was not recognized.
This error can be also recognized from this toolbar:
Ensure whether you have the correct .NET Workloads installed with the terminal command:
sudo dotnet workload install maui
Check whether you have the latest .NET SDK installed on your machine, from the Microsoft’s official website.
Ensure you have enabled “Use the .NET 8 SDK if installed” in the Visual Studio for Mac’s preferences.
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:
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.
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.
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!
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.
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.
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.