Limitations When Launching .NET MAUI Windows App via Custom URI Scheme

I've added the following entry to the Package.appxmanifest for my .NET MAUI Windows app to support activation via a custom URI scheme:

After investigating this setup, I observed the following limitations:

Key Findings Windows Focus Restrictions: When the app is already running and is triggered via the custom URI (e.g., abcapp://), Windows does not bring the app window to the foreground. This seems to be a restriction imposed by the OS, requiring explicit user interaction to shift focus to the app.

Lack of Built-in URI Activation Support in .NET MAUI: .NET MAUI currently lacks built-in support or abstraction for handling URI scheme activations on Windows, unlike other platforms like Android and iOS which provide URI intent/deep link handling through MAUI APIs.

Question Are there any recommended workarounds or best practices to: Bring a running .NET MAUI Windows app to the foreground when activated via a URI? Properly handle custom URI activation in MAUI on Windows without relying on platform-specific code? Any guidance or examples would be appreciated!