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 project is missing

Confirm that you are signed in to the same DialStudio account.
Open Projects and wait for the cloud library to load.
Open Profile → Sync. Choose Sync now if syncing is paused or needs attention.
Open Cloud Trash if the project may have been deleted.
If the project existed only on this device, return to the same browser profile or desktop app where you created it.

If local browser data was cleared before the project reached the cloud, restore an exported transfer file through Settings → Storage & data → Import projects. Unsynced work without a backup 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, exit Preview and check its Rules for a matching Hide condition. Change the relevant sample value or scenario to confirm when the rule applies.

An image will not upload

Choose a PNG, JPEG, WebP, or AVIF 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

Open Garmin SDK Manager and install a Connect IQ SDK. Installing the manager alone does not install the compiler.
Select the installed SDK as active.
In desktop, open Settings → Build & install → Check again.
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, activity source, or resource: Open the editor's checks. Replace or remove the named element, formula source, alert, or FIT field, 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.

Data Field value is missing

Check the activity state first. GPS, pace, power, cadence, heart rate, and altitude can be unavailable before the activity settles, while paused, or when a sensor disconnects.

In Studio, preview Missing data, Paused, lap transition, and workout scenarios. Check whether the target watch supports the selected source. If not, use another source or change the missing-data fallback.

Custom FIT data is not visible after sync

Confirm the project includes the expected FIT field, message type, units, and data type. Build and install the latest version, then record a short test activity on the target watch.

Record fields follow the watch's recording schedule; they are not saved several times per second. Lap fields need a completed lap, and session fields need the activity to finish or reset. Some synced services hide custom FIT fields even when the file contains them.

Data Field will not appear in an activity

Confirm the .prg was installed to the exact target watch and that the activity supports Connect IQ Data Fields. Add the field from the activity's data-screen settings, not from the watch-face menu.

Device not detected

Use DialStudio desktop and open the install view for a completed build.
Connect the watch directly with a data-capable USB cable. If it only charges, use another cable or port.
Choose data-transfer mode if the watch asks, then wait for the operating system to recognize it.
Close other apps using the watch’s connection and reconnect.
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.