Source note: LemonLoader is independent. Project-specific facts below are limited to information published by the LemonLoader repository, releases, or wiki; general troubleshooting advice is identified by context.
Before updating
- Back up important app data.
- Check the latest GitHub release tag and read its notes.
- Confirm whether the update is core or installer-only.
- Keep a path back to a clean app install.
Use the release’s own instructions
Older release notes can contain version-specific instructions. For example, 0.6.5 told users to uninstall the old installer before updating. Do not assume that instruction applies forever; read the note for the version you are actually installing.
After updating
Patch a clean/known app state when possible, then verify the first launch, permissions, and logs. If the app previously worked and now fails, compare the exact release tag and target app version before changing multiple variables at once.
Avoid unofficial updater claims
This site does not provide an automatic updater, “latest APK” API, or mirror. The release page is the update reference.
Change one layer at a time
If a working setup matters, avoid updating the target app, LemonLoader, and every mod on the same day without a baseline. Update one layer, test, and record the result. That simple sequence makes rollback and bug reporting far more useful.
Preserve the old working state
Keep the old release tag and a list of mods/configuration that were known to work. Do not rely on memory. If the new installer patches successfully but the app behavior changes, you can then compare logs and versions instead of starting from scratch.
Always re-read the current release notes. Version-specific instructions—such as uninstalling an older installer before a particular update—should not be generalized to releases that do not say the same thing.
Recommended next step
For a clean path through the project, use the verified download page, follow the installation guide, and keep the logging guide available for troubleshooting.