AppInstance.GetCurrent().GetActivatedEventArgs().Data returns "null" on command line activation

[myblindy]

Describe the bug

I enabled app execution aliasing to get the project to be callable from the command line (for jump lists), and that part works fine.

However sending command line arguments don't seem to be caught by the child app with a AppInstance.GetCurrent().GetActivatedEventArgs(). In fact, the Data property is "null" (quoted, because it's not actually null, it's some allocated IInspectable with nothing else inside and I'm assuming that's what a null looks like in WinRT).

I'm receiving the same "null" value both by launching it from VS the first time and from the jump list as a child process.

Steps to reproduce the bug

1. Clone https://github.com/myblindy/EasyDownloader2/tree/feature/jumplists
2. Run the application in debug mode, the main window should appear as normal (however in Program.DecideRedirection the activated data is already "null").
3. From the jump list on the task bar, click the custom entry:
   
4. The second application starts, sends a redirect command (with "null" data, since that's what it can see) which is then correctly caught by the main application and then ignored as unhandled.

Expected behavior

For step 2, I should see an actual Data property with an empty string for command line arguments. For step 4, I should see the correct command line arguments as well. Note that the arguments are caught correctly by the Main function itself, but I am unable to construct my own object with it to send to the main application.

Screenshots

No response

NuGet package version

Windows App SDK 1.2.1: 1.2.221116.1

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

Visual Studio 2022-preview

Additional context

No response

[KiyanYang]

I have the same problem.

Version:

• Windows 11 22H2 (22621.1265)
• Visual Studio 2022 (17.4.5)
• Windows App SDK 1.2.230118.102

And AppInstance.GetCurrent().GetActivatedEventArgs().Data.GetType().FullName get WinRT.IInspectable.

Now I use Environment.GetCommandLineArgs() as a temporary solution.

[MuyuanMS]

@myblindy Thanks for reporting the issue! I've cloned the code but had some trouble building and run it as part of old issue cleanups.

Given I've seen changes after the issue was reported (it has been years since reporting after all), so I just hope to confirm whether you know the issue still exists currently with WinAppSDK 1.6? If so, could you provide with me a minimal reproducible example?

Same goes for @KiyanYang - If the issue still exists on 1.6, could you give more details (e.g. whether it's packaged or unpackaged, code snippets, etc.) on it?

[MuyuanMS]

Close the issue for now - if there's confirmation on it still occurring, feel free to create new issue with repro steps/code