maui-deep-linking

Configure deep linking in MAUI apps for Android and iOS.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Petelids/Sudoku --skill maui-deep-linking-petelids
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-deep-linking
Source: https://github.com/Petelids/Sudoku/tree/main/skills/maui-skills/maui-deep-linking
Command: npx skills add https://github.com/Petelids/Sudoku --skill maui-deep-linking-petelids

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MAUI apps often cannot handle external URLs or app-to-app navigation consistently across Android and iOS. This Skill provides a guided approach to implement deep linking, app links, universal links, and custom URI schemes so users can open a specific screen directly from a URL.

Core Features & Use Cases

  • Android App Links with Intent Filters and domain verification
  • iOS Universal Links with Associated Domains and AASA files
  • Custom URI schemes and Shell routing integration
  • Testing and validation on physical devices

Quick Start

Configure deep linking in a MAUI app by enabling Android and iOS link handling, then test with sample URLs on a device.

Frequently Asked Questions about maui-deep-linking

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

FAQPage Schema
How do I implement deep linking in a MAUI app to route external URLs to in-app screens?

To implement deep linking in a .NET MAUI app, you configure platform-specific settings like Android Intent Filters and iOS Associated Domains, then use MAUI lifecycle handlers to map the external URLs directly to your Shell routes for in-app navigation.

What is the difference between Android App Links and iOS Universal Links in MAUI?

Android App Links use Intent Filters and Digital Asset Links for domain verification, whereas iOS Universal Links require Apple App Site Association (AASA) files and Associated Domains to securely route external URLs to your MAUI app screens.

How do I configure custom URI schemes and Shell routing in a MAUI application?

Configuring custom URI schemes in a MAUI application involves registering your custom protocol in the platform-specific project files and mapping the URI structure to Shell routes using MAUI lifecycle handlers for app-side routing.

Do I need to host a digital asset links file or AASA file to verify my MAUI app links?

Yes, domain verification requires hosting specific files. Android requires a Digital Asset Links JSON file, and iOS needs an Apple App Site Association (AASA) file hosted on your web domain to authorize universal links and app links.

Why are my universal links not opening the correct screen on physical iOS devices?

Universal links often fail on physical iOS devices due to improper AASA file formatting, missing Associated Domains entitlements, or unregistered Shell routes, making physical device testing and validation essential for proper app-side routing.

Can I use the same deep linking configuration for both Android and iOS in MAUI?

No, domain verification and app-side routing configurations differ per platform, requiring Android Intent Filters with Digital Asset Links and iOS Associated Domains with AASA files, though both map directly to shared MAUI Shell routes.