-
-
Notifications
You must be signed in to change notification settings - Fork 330
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
Notification platform is unavailable error #1772
Comments
Here is the log file: |
When the app crashed, I was just trying to change a few settings and trying it out. Nothing radical. |
Have you tried disabling the Explorer module? |
If I turn off the Explorer plugin, FL stops showing results altogether! |
@raindropsfromsky Sorry, I'm confused about your issue. Can you please describe it a little bit? Can you start FL or not (crashing before starting)? |
Looks like something wrong with your clipboard. @taooceros Is it similar to the clipboard shortcut issue you've fixed before? |
This happened only once, while I was tinkering with the plugins and settings. It is not repeatable. |
This error seems to relate to the notification module (and probably the windows version you are using). Could you check typing "reload plugin data" and see whether the error is reproducible? |
I tried this, and got a confirmation message. FL works fine after that. That said, I must also mention that after I got that error message a few days ago, I have been using FL heavily, but never faced any crash. All these days I haven't reloaded the plugin data, and yet FL worked stable. In other words, the crash seemed to be one-off. |
Yeah it seems like the toast notification is not available in your computer, but flow didn't use that much so it's not gonna affect your daily usage. Could you share which windows version you are using? |
I am using Windows 11 Home 64 bit |
This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen. |
I sometimes run into this error during startup in debug mode as well. @taooceros @VictoriousRaptor Have you also run into this error before? |
Sometimes in debug mode. |
I experience this issue. I uninstalled and reinstalled Flow Launcher. It crashes as soon as I start the setup. |
Taking a look at this issue, it appears to be from the Bump ModernWpfUI from 0.9.4 to 0.9.6 change. This causes flow's notification to error out, and in turn causes the following critical issues when error happens on user machine:
Code location: For me only reproducible via debug mode while running Visual Studio. Error does not appear if running a build from the repo's ci pipeline. Reproduce in Visual Studio debug mode: Downgrading ModernWpfUI from 0.9.6 to 0.9.4, clean and rebuild then trigger notification, the error no longer is thrown. Environment: |
Additional investigation to above: I can replicate the issue from v1.12.0 onwards. Removing the Programs plugin will also stop the error from happening, which leads me to think it could be related to this microsoft/CsWinRT#623 (comment) |
Traced the error to this change made to the way we load plugin dlls #367, reverting to the commit before this change will also resolve the error. |
Checks
Problem Description
Please open new issue in: https://github.com/Flow-Launcher/Flow.Launcher/issues/new
Flow Launcher version: 1.11.0
OS Version: Microsoft Windows NT 10.0.22621.0
IntPtr Length: 8
x64: True
Python Path:
Node Path:
Date: 01/10/2023 01:21:05
Exception:
System.Runtime.InteropServices.COMException (0x803E0105): The notification platform is unavailable. (0x803E0105)
at WinRT.ExceptionHelpers.g__Throw|20_0(Int32 hr)
at ABI.Windows.UI.Notifications.IToastNotificationManagerStaticsMethods.CreateToastNotifier(IObjectReference _obj, String applicationId)
at Windows.UI.Notifications.ToastNotificationManager.CreateToastNotifier(String applicationId)
at Microsoft.Toolkit.Uwp.Notifications.ToastNotificationManagerCompat.CreateToastNotifier()
at Microsoft.Toolkit.Uwp.Notifications.ToastContentBuilder.Show(CustomizeToast customize)
at Microsoft.Toolkit.Uwp.Notifications.ToastContentBuilder.Show()
at Flow.Launcher.Notification.Show(String title, String subTitle, String iconPath) in C:\projects\flow-launcher\Flow.Launcher\Notification.cs:line 35
at Flow.Launcher.PublicAPIInstance.<>c__DisplayClass13_0.b__0() in C:\projects\flow-launcher\Flow.Launcher\PublicAPIInstance.cs:line 97
at System.Windows.Threading.Dispatcher.Invoke(Action callback, DispatcherPriority priority, CancellationToken cancellationToken, TimeSpan timeout)
at System.Windows.Threading.Dispatcher.Invoke(Action callback)
at Flow.Launcher.PublicAPIInstance.ShowMsg(String title, String subTitle, String iconPath, Boolean useMainWindowAsOwner) in C:\projects\flow-launcher\Flow.Launcher\PublicAPIInstance.cs:line 95
at Flow.Launcher.PublicAPIInstance.ShowMsg(String title, String subTitle, String iconPath) in C:\projects\flow-launcher\Flow.Launcher\PublicAPIInstance.cs:line 91
at Flow.Launcher.Plugin.Explorer.ContextMenu.<>c__DisplayClass13_0.b__4(ActionContext ) in C:\projects\flow-launcher\Plugins\Flow.Launcher.Plugin.Explorer\ContextMenu.cs:line 134
at Flow.Launcher.Plugin.Result.ExecuteAsync(ActionContext context) in //Flow.Launcher.Plugin/Result.cs:line 219
at Flow.Launcher.ViewModel.MainViewModel.OpenResultAsync(String index) in C:\projects\flow-launcher\Flow.Launcher\ViewModel\MainViewModel.cs:line 276
at CommunityToolkit.Mvvm.Input.AsyncRelayCommand.AwaitAndThrowIfFailed(Task executionTask)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
To Reproduce
Screenshots
No response
Flow Launcher Version
v1.11.0
Windows Build Number
10.0.22621 Build 22621
Error Log
The text was updated successfully, but these errors were encountered: