Skip to main content

​
Download fails or is interrupted

  • Check that the network can reach the model download site.
  • On the Models page, view the error for the download task; after the network recovers, click Retry or Resume.
  • E-DL-NET: network interruption or timeout.
  • E-DL-SRC: the download source rejected the request or is unreachable; retry later or switch networks.
  • E-DL-DISK: insufficient disk space; clear space first.

​
Insufficient disk space

  • Check the disk that stores models, not just the system drive. macOS stores them under ~/.edge0 by default, and Windows under %USERPROFILE%\.edge0.
  • Stop any download or conversion in progress first, then clear files you do not need.
  • Before deleting a model in the desktop app, click Unload model on macOS or Evict on Windows, then click Delete.
  • On macOS, after deleting a model you can run edge0 gc with the bundled command-line tool to free files that are no longer used. For the tool’s location, see the macOS Guide.
  • iOS requires checking space on both the Mac and the iPhone; Android requires checking both the computer and the device.

​
The model is downloaded but will not load

The model file formats differ by platform and are not interchangeable.

​
Windows model conversion fails

  1. Check %USERPROFILE%\.edge0\logs\convert-*.log and find the earliest error.
  2. If it is a missing dependency or a path that cannot be found, fix the environment first as in the Windows Guide.
  3. If it is a missing file or a checksum error, delete the download task and download again.

​
The first turn is slow, or it slows down after a while

Loading a model can take time. After it is loaded, the first turn of a new topic and longer inputs may increase the wait before generation begins. For the specifics on Android, see the Android Guide. You can try:
  • Wait for the current load to finish; do not click load or send repeatedly.
  • Start a new chat and test with a short question.
  • Close other resource-heavy apps.
  • If the device is hot, let it cool down and try again.
  • Use 8B first to determine whether the issue is caused by the larger model’s resource requirements.
If you also see an error, an unexpected app exit, or no progress for an extended period, continue with the sections below.

​
The app crashes or the engine exits

  • Note the error message and the time it happened, then reopen the app and load the model.
  • Windows: check the latest engine-*.log; if it reports a missing engine binary, rebuild the engine.
  • macOS: check Environment Check on the Service page; if it reports a service version mismatch, quit and reopen the app.
  • iOS: confirm the model files are complete, reopen the app, and retry with a short question; if it still exits, obtain device logs.
  • Android: obtain device logs and look for load errors or crash information.
If the problem persists, prepare the simplest steps to reproduce it and report them.

​
Build or installation fails

  • macOS missing Metal compiler: check Xcode and the Command Line Tools, then run bash scripts/check-prereqs.sh again.
  • iOS missing Metal compiler: run xcodebuild -downloadComponent MetalToolchain, then retry.
  • iOS signing fails: verify the selected Team, unique Bundle Identifier, device trust status, and Developer Mode.
  • Android cannot find the NDK: install the NDK r28 specified in the guide and set NDK_DIR.
  • Android missing native libraries: run the engine build step successfully first, then build and install the app.
  • The system blocks the app from opening: see Security & Installation Warnings.

​
Collect diagnostics

Check Environment Check and the service status on the Service page. Logs are under:
You can also use edge0 doctor and edge0 logs with the bundled command-line tool; for the tool’s location, see the macOS Guide.