Open AyakaLoyalist opened 10 months ago
Hi,
COMExceptions are usually quite hard to debug. They can occur due to some factor outside of JASM.
But I'll try to add a fix in the next release
System.Runtime.InteropServices.COMException (0x80004005)
at GIMI_ModManager.WinUI.ViewModels.SubVms.PathPicker.BrowseFolderPathAsync(WindowEx window) in D:\a\JASM\JASM\src\GIMI-ModManager.WinUI\ViewModels\SubVms\PathPicker.cs:line 91
at GIMI_ModManager.WinUI.ViewModels.StartupViewModel.BrowseGimiModFolderAsync() in D:\a\JASM\JASM\src\GIMI-ModManager.WinUI\ViewModels\StartupViewModel.cs:line 159
at CommunityToolkit.Mvvm.Input.AsyncRelayCommand.AwaitAndThrowIfFailed(Task executionTask)
at System.Threading.Tasks.Task.<>c.
System.Runtime.InteropServices.COMException (0x80004005) at GIMI_ModManager.WinUI.Services.BaseProcessManager`1.PickProcessPathAsync(Window windowHandle) at GIMI_ModManager.WinUI.ViewModels.CharactersViewModel.StartGenshinAsync() at CommunityToolkit.Mvvm.Input.AsyncRelayCommand.AwaitAndThrowIfFailed(Task executionTask) at System.Threading.Tasks.Task.<>c.b128_0(Object state)
at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.b 0()