L Lomi documentation

Lomi source package

Troubleshooting

Use these focused checks when Docker, Android Studio, the admin wizard or app connection fails.

Quick checks

Match the error to a step

What you seeWhat to check
docker: command not found or Compose errorInstall Docker Engine and the Compose plugin, start Docker, then rerun sh scripts/setup.sh inside server/backend.
/health/ready does not respondRun docker compose ps and docker compose logs api worker moderation migrate in server/backend. Read the first failing service and its exact error.
Admin wizard asks for licenseCopy the wizard installation ID, recover your paid checkout order if needed, and issue a key using the exact admin origin. For local setup, use http://localhost:8080. For a production domain, use its exact HTTPS origin and configure LICENSE_PUBLIC_KEY in the server environment.
Missing keystore.propertiesCreate the private file in outer app/ and check that storeFile points to a keystore you created.
Google Services JSON errorAdd your Firebase files to app/app/src/debug/ and app/app/src/release/. Check the package IDs match each variant.
App cannot reach APICheck the API health URL on the host, then check apiBaseUrl, emulator host 10.0.2.2, USB adb reverse and HTTPS for release builds.
Build dependency download failsConfirm internet access, Gradle JDK and SDK versions, then retry sync. The first build must download pinned dependencies.

Collect useful details for support

Send lomi@amixmon.com the guide step, operating system, exact error, and the command you ran. For server issues, include the relevant container name and a short redacted log excerpt. For Android issues, include the Gradle task and build variant.

Remove passwords, API secrets, private keys, wallet recovery phrases, personal account data and .env values from screenshots and logs before sharing them.