-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since Fall Creators Update, AppIds need to be valid #1
Comments
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. |
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 ... |
So using This seems like something that would get broken again in a new update. |
I think this is again broken, at least the simple example does not seem to produce anything. Windows 10 update 2004. |
Simple example in the docs doesn't produce anything for me either. No error message, program executes, exits and no notification is shown. |
Different issue. |
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. |
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.
The text was updated successfully, but these errors were encountered: