Environment Variables won't save

[DannyJacoby]

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?

7.1

What operating systems are you seeing the problem on?

Windows, MacOS

Describe the bug

In this current build, I can't modify/add in custom environment variables. I can add them in the desktop application's window, however they aren't saved.
I've gone into the settings.json file to add them, however I can't seem to get the format correct as I keep getting this error:
theseus::state::settings: Failed to load settings file: Serialization error (JSON): invalid type: string "-XX:+UnlockExperimentalVMOptions", expected a tuple of size 2 at line 12 column 58.

Steps to reproduce

The easiest method to reproduce this issue is to go into the application, go to the settings (global settings or individual modpack, it can be replicated in either), and then enter any java specific settings (like "-XX:+UnlockExperimentalVMOptions").
These settings will not be saved, and if you were to try and input these settings specifically into the settings.json file, the launcher will have to recreate the settings file and will log the above error.

Expected behavior

That any custom environment variables would be saved.

Additional context

No response

[kalixdrake]

I am having the exact same issue, neither environmental variables nor arguments get saved, global or modpack independent, they simply are as if were non existent.
Have you been able to solve it in any way?

[Awakened-Redstone]

Environment variables expect to follow the format key=value separated by spaces, the mentioned text you tried is a JVM flag, that should be put in Java arguments and not Environment variables

Environment variables are meant to be used for variables that are passed to the game, such as --quickPlayMultiplayer="localhost"

[Jasper3346]

I have the same problem, although on a different system (Fedora [Linux], official version installed from the website).

When I enable the Environment variables option, enter a value, switch to another tab in the settings, and then return to the Java and memory tab, the input field is empty again. In contrast, the field above, Java arguments, correctly saves the entered text.

Additionally, both mentioned options cannot be disabled once they have been enabled. While the text can still be removed, the checkbox itself cannot be unchecked. You can test this the same way as before.

[Prospector]

This should be fixed now