Repository navigation
Releases: FlameLaunchers/FlameLauncher-Android
Release list
v2.5.16 — Minecraft 26.4 snapshots
What's new
- Minecraft 26.4 snapshots start. A version id like
26.4-snapshot-3splits into26and4-snapshot-3, and reading that second part as a plain integer gave nothing — so 26.4 was treated as 26.0, missed the SDL and LWJGL 3.4.3 stack, and launched on LWJGL 3.3.6 instead. The game died immediately withNoClassDefFoundError: org/lwjgl/sdl/SDLPlatform; the cacio lines in the crash report were a consequence, not the cause. Version numbers are now read digit by digit, so snapshot, pre-release and rc suffixes no longer hide them, and five tests cover the shapes. - Carries the previous fix as well: on Java 24 and newer the cacio java agent is skipped, because the
sun.misc.Unsafecalls itspremaindepends on are refused there and a failing agent takes the VM with it.
v2.5.15 — Minecraft 26.4 starts again
What's new
-
Minecraft 26.4 (and anything else on Java 24 or newer) starts again. The cacio setup loaded a java agent whose
premainoverwrites the AWT toolkit's static fields throughsun.misc.Unsafe(staticFieldBase,staticFieldOffset,putObject). Those methods are refused from JDK 24 and gone in 26, and a failing agent takes the whole VM down with it — which surfaced as a cacio error at startup.The iOS build has always run the same cacio jars without that agent, on the same Java 25, using only
-Dawt.toolkitand-Xbootclasspath/a. Android now does the same on Java 24+ and keeps the agent only for the older runtimes that still need it.
v2.5.14
v2.5.13 — CurseForge and release notes
What's new
-
CurseForge browsing works again. The API key the app shipped with had been revoked, so every request came back
403 Forbidden, and the mod and modpack lists were simply empty. A new key is in place (still encrypted in the build, never in the source). -
The notes screen shows releases instead of the repository README. It was pointed at a repository that has since gone private, so it came up blank — and release notes are what belongs there anyway. It now lists the ten most recent releases with their notes.
v2.5.12
v2.5.11 — NeoForge on 26.3
What's new
- NeoForge runs on 26.3. FancyModLoader decides it is inside a development environment as soon as it can see Minecraft's own classes on the class path, and then fails with "The patched Minecraft jar is missing" or a complaint about a missing
Minecraft-Distsattribute. The launcher now keeps the vanilla jar and the patched jar out of the way and lets the loader find them itself, the way it does on a desktop install. - Beta builds are selectable for versions that have no stable release yet. 26.3 only has beta NeoForge builds, so the list collapsed to a single row and looked as if nothing were available. When there is no stable build the five newest betas are listed instead.
v2.5.10 — Encrypted API key
What's new
- The CurseForge API key is no longer stored in the open. It used to sit in the app as plain text, where anyone could pull it out of the download with a single
stringsrun. The build now ships it encrypted (AES-256-CBC, key derived with SHA-256) and the app decrypts it in memory; the passphrase never goes near the repository. - The key itself has been replaced, so the old one is out of circulation.
v2.5.9 — NeoForge on 26.3, older Sodium builds
What's new
- NeoForge shows up for 26.3 again. The launcher worked out which Minecraft version a NeoForge build belongs to by always prefixing
1., which is only right for the old numbering (21.1.251→ 1.21.1). The 26.x builds use four parts (26.3.0.22-beta→ 26.3), so the list came back empty and NeoForge looked unavailable. - Podium is installed alongside older Sodium builds too. Sodium releases up to 0.5.3 are named
sodium-fabric-mc1.20.1-0.5.0.jar, with the Minecraft version in the middle, and the launcher did not recognise those as Sodium — so Podium was silently skipped and the game would not start at all (Sodium refuses to run on PojavLauncher-style environments without it).