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.
Permission prompt
The 0.6.5.1 release notes say patched apps can ask for file permissions on first launch and those permissions should be enabled for the documented setup to work.
Longer first boot
The installation wiki warns that the first boot can take from roughly one minute to twenty minutes or more depending on app size. Avoid repeatedly force-closing the app just because the first launch is slower than normal.
Possible first-run crash
The latest release note acknowledges that an app may crash on the first launch and suggests starting it again. If crashes continue, move to logs and compatibility checks instead of repeating patch attempts blindly.
Quest UI oddities
On Quest, the platform may show modified-app warnings or temporarily claim the app is not installed. The wiki suggests restarting the headset when the interface becomes confused.
Separate first-run behavior from long-term behavior
The first launch can involve permission prompts and initialization work that later launches do not repeat. Judge the first run by the project’s documented expectations rather than by the normal launch speed of the unmodified app. Once the first run succeeds, restart the app again and note whether the same delay or warning repeats.
Establish a clean baseline before mods
Launch the patched app before copying third-party mods or plugins. If the clean patched app works, you have isolated the loader setup from later mod problems. If it fails, logs and compatibility checks are the next useful evidence. Adding mods before this baseline only makes the failure harder to attribute.
When the platform shows its own modified-app warning, record the exact wording. Platform messages, LemonLoader logs, and installer messages come from different layers and should not be treated as interchangeable.
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.