Since Fall Creators Update, AppIds need to be valid

[Boddlnagg]

Before Windows 10 Fall Creators Update you could provide any string as AppId and it basically worked, but now it won't work anymore. This breaks the examples. See contextfree/winrt-rust#44.

[allenbenz]

Well that is disappointing, was nice that it worked without a valid id for a while.

Looks like other toast projects have mechanisms to add an AppId to the registry.

I'll take a look into that over the weekend.

[Boddlnagg]

This blogpost indicates that adding the AppId to the registry is not sufficient, which is why the BurntToast project switched to using the PowerShell AppId instead ...

[allenbenz]

So using {1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\\WindowsPowerShell\\v1.0\\powershell.exe as the appId would make it work again?

This seems like something that would get broken again in a new update.

[Ciantic]

I think this is again broken, at least the simple example does not seem to produce anything. Windows 10 update 2004.

[mthelm85]

Simple example in the docs doesn't produce anything for me either. No error message, program executes, exits and no notification is shown.

[allenbenz]

Different issue.
For some reason a windows update made it sensitive to the application closing before the toast showed.
0.2.3 will add a 10ms wait after the show to prevent that from being an issue.

[allenbenz]

Closing the issue as using the powershell id has held for the last few years as a workaround to not having an installed application/proper app id.