Please confirm the following.
What version of the Modrinth App are you using?
0.13.15
What operating systems are you seeing the problem on?
Linux
Describe the bug
When trying to import a PrismLauncher instance, the app shows "No importable instances were found at the specified path" even when the path is correct.
Looking at the source code in packages/app-lib/src/api/pack/import/mod.rs, the app expects the PrismLauncher data root folder and then automatically appends the instances subfolder by reading prismlauncher.cfg. If you provide the instances folder directly, it looks for instances/instances/ which doesn't exist.
The UI should hint that you need to provide the launcher data root, not the instances subfolder. Or alternatively, the app should detect both cases and handle them gracefully.
Suggested fix
Add placeholder text in the input field like e.g. /home/user/.local/share/PrismLauncher | /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher Or auto-detect if the user passed the instances subfolder and strip it
Environment
OS: Arch Linux, KDE Plasma Wayland
PrismLauncher: Flatpak (org.prismlauncher.PrismLauncher)
Modrinth App: Flatpak (com.modrinth.ModrinthApp)
and in terminal on Linux (im not sure if this works on another linux)
flatpak override --user
--filesystem=/home/user/.var/app/org.prismlauncher.PrismLauncher \ (change 'user' to your username on your linux)
com.modrinth.ModrinthApp
Steps to reproduce
1.Install PrismLauncher via Flatpak
2.Open Modrinth App → Import instance
3.Paste /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances → fails
4.Paste /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher → works
Expected behavior
No response
Additional context
No response
Please confirm the following.
What version of the Modrinth App are you using?
0.13.15
What operating systems are you seeing the problem on?
Linux
Describe the bug
When trying to import a PrismLauncher instance, the app shows "No importable instances were found at the specified path" even when the path is correct.
Looking at the source code in packages/app-lib/src/api/pack/import/mod.rs, the app expects the PrismLauncher data root folder and then automatically appends the instances subfolder by reading prismlauncher.cfg. If you provide the instances folder directly, it looks for instances/instances/ which doesn't exist.
The UI should hint that you need to provide the launcher data root, not the instances subfolder. Or alternatively, the app should detect both cases and handle them gracefully.
Suggested fix
Add placeholder text in the input field like e.g. /home/user/.local/share/PrismLauncher | /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher Or auto-detect if the user passed the instances subfolder and strip it
Environment
OS: Arch Linux, KDE Plasma Wayland
PrismLauncher: Flatpak (org.prismlauncher.PrismLauncher)
Modrinth App: Flatpak (com.modrinth.ModrinthApp)
and in terminal on Linux (im not sure if this works on another linux)
flatpak override --user
--filesystem=/home/user/.var/app/org.prismlauncher.PrismLauncher \ (change 'user' to your username on your linux)
com.modrinth.ModrinthApp
Steps to reproduce
1.Install PrismLauncher via Flatpak
2.Open Modrinth App → Import instance
3.Paste /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher/instances → fails
4.Paste /home/user/.var/app/org.prismlauncher.PrismLauncher/data/PrismLauncher → works
Expected behavior
No response
Additional context
No response