uno-migration-troubleshoot

Apply Uno Platform migration patterns from multi-project layouts to the Uno.Sdk Single Project model.

5|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill uno-migration-troubleshoot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uno-migration-troubleshoot
Source: https://github.com/mtmattei/UnoPlatformSkills/tree/main/uno-migration-troubleshoot
Command: npx skills add https://github.com/mtmattei/UnoPlatformSkills --skill uno-migration-troubleshoot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Migration and troubleshooting guidance for Uno Platform projects, helping teams move from multi-project setups to the Uno.Sdk Single Project model and resolve common upgrade issues.

Core Features & Use Cases

  • Step-by-step migration patterns from legacy multi-projects to Single Project with platform consolidation under Platforms/.
  • Guidance on upgrading .NET versions (e.g., net8 to net9) and ensuring Uno.Sdk compatibility across Wasm, Android, iOS, and Desktop.
  • Comprehensive troubleshooting coverage for common errors (UNOB0011/UNOB0013, Uno.Extensions 5.2+ changes, Wasm bootstrapper migrations) including tooling recommendations.

Quick Start

Provide your Uno project details to receive a migration and troubleshooting plan tailored to your environment.

Frequently Asked Questions about uno-migration-troubleshoot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate an Uno Platform project from a multi-project layout to the single project model?

To migrate an Uno Platform project to the single project model, you must consolidate platform-specific projects under a unified Platforms/ directory and update your SDK references to the Uno.Sdk. This centralizes Wasm, Android, iOS, and Desktop targets into one structured solution.

Why do I get UNOB0011 or UNOB0013 build errors after updating my Uno.Sdk?

UNOB0011 and UNOB0013 build errors occur when your Uno Platform project configuration conflicts with upgraded Uno.Sdk expectations. You can resolve these build errors by applying the correct single project migration patterns and verifying your target framework alignments.

How do I upgrade my Uno Platform project from .NET 8 to .NET 9 safely?

To upgrade your Uno Platform project from .NET 8 to .NET 9, you must update your global.json file and ensure your Uno.Sdk version supports the new target framework. Running a uno-check validation provides a safe migration workflow with rollback capabilities.

What do I need to change for MSAL authentication when upgrading to Uno.Extensions 5.2?

Upgrading to Uno.Extensions 5.2 requires updating your MSAL authentication configuration to match the new extension architecture. You must apply the specified troubleshooting patterns to adjust authentication initialization and ensure compatible runtime behavior across your targets.

Does migrating to the Uno Platform single project model require updating the Wasm bootstrapper?

Migrating to the Uno Platform single project model requires updating the Wasm bootstrapper to align with the consolidated Uno.Sdk. Applying the correct bootstrapper migration steps ensures your WebAssembly target initializes properly without runtime errors.

What is the best way to troubleshoot Wasm build errors in an Uno Platform single project?

The best way to troubleshoot Uno Platform Wasm build errors is to run the wasm-tools workload update and verify your global.json configurations. These safety checks identify missing tooling dependencies and ensure robust migration completion across your platforms.