Troubleshooting

Find the symptom below. After changing a setting or fixing a file, repeat the step that failed.

Build is unavailable in the browser

Building and installing need the desktop app. Installing Java or Garmin’s SDK will not enable the browser’s Build button. You can continue designing and export a project backup. Check desktop availability before setting up build tools.

My browser project is missing

1. Open the same Studio address in the same browser profile where you created the project.
2. Check Projects. Another browser, private window, or computer has separate storage.
3. If you have a transfer file, open Settings → Storage & data → Import and restore the project.

If site data was cleared or a private session ended, the project may be gone. Without an exported backup, cleared browser data may not be recoverable.

A layer is missing or will not move

Check that you are editing the intended display mode. In Layers, check whether the item is hidden or locked. Unlock it before changing its position. If another layer covers it, move the item forward in the layer order.

If the layer disappears only for certain data values, check its Rules for a matching Hide condition.

An image will not upload

Choose a PNG, JPEG, or WebP file under 5 MB. Studio converts the image for the watch; the converted file must also fit its resource limit. Reduce the image’s dimensions or detail if the error says the encoded image is too large, then upload the smaller file.

SDK not found

1. Open Garmin SDK Manager and install a Connect IQ SDK. Installing the manager alone does not install the compiler.
2. Select the installed SDK as active.
3. In desktop, open Settings → Build & install → Check again.
4. If detection fails, use the advanced path picker. Choose the active SDK folder containing bin/monkeybrains.jar, or the ConnectIQ folder containing current-sdk.cfg.

If the SDK is found but the watch is missing, download that exact model’s device profile in SDK Manager. Recheck setup before building.

Signing key issues

In Settings → Build & install, check Your signing key. Choose Generate key for your first key, or Advanced → Import key to restore an existing one.

Import the original DER or PEM private-key file. A certificate, public key, or empty file cannot sign a build. If the import fails, check the file type and read the error details. Do not replace an existing key just to clear an error.

Keep a secure backup. Never include key contents in a support message.

Build failed

Open the build’s error details and start with the first error that names a cause.

• Missing target: Install the exact device profile in SDK Manager and check the project’s device.
• Unsupported layer or resource: Open the editor’s design checks. Replace or remove the named element, then rebuild.
• Output unavailable: Check free space and write access to the local output folder.
• Java unavailable: Check that you installed a complete desktop package with its bundled runtime. Changing system Java may not fix a missing bundled runtime.
• File moved or deleted: Build again to create a new watch file. Install from the new build record.

If the error is unclear, build a simple template for the same device. If that succeeds, compare the failing project’s images, fonts, layers, and design checks. Keep a backup before removing content.

Device not detected

1. Use Dial Studio desktop and open the install view for a completed build.
2. Connect the watch directly with a data-capable USB cable. If it only charges, use another cable or port.
3. Choose data-transfer mode if the watch asks, then wait for the operating system to recognize it.
4. Close other apps using the watch’s connection and reconnect.
5. Check detection in Studio. MTP watches may not appear as Finder disks or drives with letters.

See the macOS and Windows install notes for platform details.

Transfer failed

Wait until the active transfer has stopped before unplugging. Check the reported error: confirm the device is connected, the destination is writable, and the build file still exists. Close competing transfer apps, reconnect, and start the install again from the build record.

If the build file is missing, rebuild the project first. Keep the cable connected until Studio reports Installed.

My face looks different on the watch

Confirm that you installed the latest build for the exact model. Then check the affected part:

• Text is cut off: Allow more room for real values and check font size.
• Data is missing: Confirm that the watch supports that source and has the required permissions or sensor data.
• Color or visibility changes: Check appearance rules and the active display mode.
• Always-on looks different: Review the device’s power limits and the editor’s design checks.

If the face does not load, switch to another watch face. Back up the project, simplify the affected layers, then build and install again.

Details to keep when asking for help

Record the action, exact error text, watch model, operating system, and whether you used browser or desktop. For build errors, include the SDK version. Remove private keys and personal paths from shared files.