CurseForge mod update check hangs after API request finishes

Operating System

macOS

Version of Prism Launcher

Prism Launcher 11.0

Version of Qt

6.9.3.

Description of bug

When checking installed mods for updates, Prism Launcher gets stuck while checking CurseForge mods.

The CurseForge API request appears to finish downloading successfully. The progress display reaches the full response size, for example:

3.01 KiB / 3.01 KiB

but Prism never moves past the request and the update check does not finish. The only way to exit the task is to press Abort.

I originally thought this was caused by one specific mod, but after removing that mod, the updater became stuck on another CurseForge mod instead.

I have reproduced the behavior with multiple CurseForge project IDs, including 1673262, 1684339, and 1683228.

This started happening for me after updating from Prism Launcher 10.0.3 to 11.0.

Expected behavior: after the CurseForge API response finishes downloading, Prism should process the response and continue checking the remaining mods.

Actual behavior: the API response reaches 100%, but the update task remains stuck indefinitely.

Steps to reproduce

Open a Minecraft 26.3 instance containing CurseForge-installed mods. Open Edit Instance → Mods. Select the installed mods and click Check for Updates. Wait until Prism starts checking a CurseForge project. The CurseForge API request reaches its full downloaded size. Prism remains stuck on that request indefinitely. Pressing Abort is required to stop the update check. Removing the mod where it became stuck causes the same behavior to occur with another CurseForge mod.

Other information

Please fix this for god's sake, screw the duplicates, you guys are refusing to fix a very big bug in the Launcher.

This issue is unique

• I have searched the issue tracker and did not find an issue describing my bug.