Modrinth App freezes when opening instance folder if default file explorer is OneCommander
Opened this issue · 2 comments
Please confirm the following.
- I checked the existing issues for duplicate problems
- I have tried resolving the issue using the support portal
- I have ensured my Modrinth App installation is up to date
What version of the Modrinth App are you using?
0.10.16
What operating systems are you seeing the problem on?
Windows
Describe the bug
If you have OneCommander set as your default file explorer, then opening a Minecraft instance folder through the Modrinth App will freeze and crash the Modrinth App.
Steps to reproduce
- Install OneCommander (direct from website, this does not affect Microsoft store version as it cannot be set as default file explorer)
- Open OneCommander, click settings in bottom left
- Click the "advanced" tab
- Check the "register as a default file manager" box and click "ok" on any boxes that pop up
- Open Modrinth App
- Click on any instance
- Click the 3 stacked dots in the top right
- Click "open folder"
The folder will successfully open in OneCommander. However, without fail, the ModrinthApp will freeze and stop responding after this and must be force closed. Sometimes OneCommander will also stop responding until Modrinth is closed
Expected behavior
Modrinth App shouldn't freeze/crash
Additional context
No response
I seem to have the same issue with Windows Explorer.
open modpack instance > click open folder > app doesn't respond. Then when I give it inputs it goes to not responding
I've never had this issue on Windows Explorer. It happened as soon as I changed my default file explorer to OneCommander.