Repository navigation
fix: use the embedded CurseForge API key in local debug builds - #455
Merged
Merged
Conversation
Local builds had an empty curseforge.api_key, so every CurseForge request returned 403. Local debug builds now fall back to the same obfuscated key that LeviLauncher for Windows embeds. Release, beta and CI builds still use only local.properties. CurseForge 401/403 responses now say whether the key is missing or was rejected.
futrime
deleted the
claude/curseforge-403-levilauncher-windows-bcca15
branch
November 10, 2026 14:37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Local builds have an empty
curseforge.api_keyinlocal.properties. Every CurseForge request then sends an emptyx-api-keyheader, and CurseForge returns 403. LeviLauncher for Windows does not hit this because it embeds an obfuscated key (internal/curseforge/apikey.bin).Changes
app/curseforge-debug-apikey.bin, the same obfuscated key the Windows launcher embeds (base64, then XOR0xAF).app/build.gradlefalls back to that key only when all of these hold:curseforge.api_keyis emptyCIenvironment variable is not setlocal.properties.CurseForgeClientnow says, on 401/403, whether the key is missing from the build or was rejected.Testing
CI=true: 0:app:compileDebugJavaWithJavacpasses. The native build was skipped.