Infinite loop when creating forge instances with versions before 1.6.1

[QuantumCoded]

• [x] I searched the issue tracker for other issues covering my case
• [x] Can reproduce with a fresh instance I'm hesitant to say it's purely launcher issue, more like a mirror issue causing the launcher to act weird, but it CAN be reproduced on a fresh install

Describe the Bug When trying to create an instance using forge with a version before 1.6.1 results in an endless loop of "Downloading game files...", "Installing forge...", repeat. Every loop gives this warning in the console: Missing resource: /home/[USER]/.config/gdlauncher_next/datastore/libraries/net/minecraftforge/[MCVER]-[FORGEVER]/[MCVER]-[FORGEVER].json

To Reproduce Steps to reproduce the behavior:

1. Go to 'Add New Instance'
2. Click on 'Select a version'
3. Click on 'Forge'
4. Scroll down to before '1.6.1' and select any version
5. Press the right arrow to create the instance
6. Launch the instance (if the instance created "successfully")

Resulting Behavior Using the steps above results in one of the following:

1. The instance is created with the warning "No installer found in temp or hash mismatch. Need to download it.", but when launched starts the endless loop stated earlier
2. The instance is created with no warning, but when launched starts the endless loop stated earlier
3. The instance is created with an AxiosError failing to HTTP GET a resource, but when launched starts the endless loop stated earlier
4. The instance is not created and fails with AxiosError: Request failed with status code 404

Expected Behavior The instance is created and launches properly OR The instance is not created and fails with an appropriate error message

Operating System

• OS: Arch Linux
• Launcher Version: 1.1.29
• Java Version: N/A (The game never starts)
• Minecraft Version: <1.6.1
• Mod Loader: Forge

[MrEAlderson]

Bump, I have the same problem as well. Makes GDLauncher unusable.

[Eskaan]

Do not bump issues by creating messages. React on them. Only write messages if you have content to add to the conversation. Also my guess you'll have to update your launcher.

[MrEAlderson]

Do not bump issues by creating messages. React on them. Only write messages if you have content to add to the conversation. Also my guess you'll have to update your launcher.

Why am I not allowed to comment that I also have the problem, lol? That's common practice.

The launcher isn't auto-updating itself? Or how else am I supposed to have an old version.

And I also noticed that this is only the case when I run with Java 8. Vanilla runs just fine on Java 17, unfortunately Forge doesn't support Java 17 at 1.12.2. QuantumCoded and I might have the same problem as https://github.com/gorilla-devs/GDLauncher/issues/1428

[Eskaan]

If you don't provide new information to the issue, it is preferred (maybe only on this repo?), if you react to the issue, most commonly with a thumbs up emoji.

I think the problem with your version is, that @killpowa does no longer pay for the certificate for our application and thus you'll have to upgrade once manually to a version that is unsigned. I am not sure about that, you'll have to contact him for more information.