PhoenixDevelopers

Skill troubleshooting

On this page

Developer guide · Workflow · SDK

Read the exact error code and the exact request status before trying again. Host validation does not execute your app or prove it is safe. An upload is not an installation; approval is not proof that startup completed. Never edit inventory, identity, approval or policy journals to bypass a refusal.

Common kit messages

Exact message / codeWhat happenedNext action
Skill request failed: unknown_templateUnknown starterUse hello, touch-ui, voice or network-service with --template, or leave it out for hello
Skill request failed: invalid_optionDuplicate, unsupported or ambiguous flagsRead --help; pass each option once
Skill request failed: EEXISTProject/output already existsUse a fresh name or output directory; never overwrite a packed artifact
Skill request failed: invalid_app_manifestAuthor manifest has unknown fields or bad names/declarationsUse the exact app.json fields; Store release fields such as releaseId, reviewId or signatures do not belong in it
Skill request failed: app_icon_ref_invalidIcon declaration is incomplete or invalidDeclare all three of iconApi, icon and iconImage, or none; see v2 icon rules
Skill request failed: invalid_file_listFile list missing/duplicated or not including app.jsonExplicitly list all shipped files, including entry and assets
Skill request failed: test_native_syntax_invalidA listed .js does not compile for the chosen parserUse CommonJS/Node 6 syntax and check every dependency with --syntax-node
Skill request failed: invalid_syntax_runtimeLegacy parser path/version is wrong or unusableSupply an absolute trusted local Node 6.5.0 executable; keep Node 20+ for the kit
Skill request failed: test_native_binary_forbiddenBinary module in packRemove .node / .so; use pure JavaScript/data
Skill request failed: test_native_scripts_forbiddenA package has scriptsBuild on your computer and ship script-free runtime dependencies
This Jibo can't install skill test builds: its info has no native in localKinds. Check that Jibo runs its current software.Jibo's info does not offer test buildsRun info and check localKinds; Jibo's current software (13.8.0) reports native
Checking the packed skill on JiboRobot-side validation, not approvalWait for the next request state; do not assume upload success means installation
Tap Install full-access test on JiboPhysical review waitingOpen Test builds if the automatic idle prompt is not visible; read permissions and final warning
Tap Remove test build on JiboRemoval waiting for final tapConfirm the selected keep/erase choice and tap the final button
Waiting for Jibo to reconnect; request <id> is still being checkedSoftware may be restarting or SSH temporarily unavailableLet the kit reconnect; preserve the printed request ID
Request <id>: pending_restartApproval is recorded; the CLI is waiting for Jibo's restart/trialLet the kit follow the request. The wait can end in a startup failure or timeout as well as success. Do not tap again for this progress state
Skill request failed: approval_timeout (request <id>)Computer wait expiredRead that request with status; the timeout did not cancel it

The literal <id> above represents the request ID printed by your command; copy that exact value. Do not substitute a Store release ID or a project ID.

Robot refusal and recovery

Code / exact screen wordingNext action
unsupported_firmware, test_manager_unavailable, test_runtime_unavailableUse Jibo's current software (13.8.0), which advertises protocol 1 and test builds. Wait for normal startup; do not copy a replacement installer onto an older release
robot_path_mismatchCompare beRoot, runtimeNode and stateRoot from info with your options; supply all differing paths explicitly
ssh_unavailable, ssh_or_robot_failed, ssh_timeout, ssh_stream_failedCheck OpenSSH, authorized developer access, address, credentials and host key. Read status after reconnecting
test_builds_disabled / Turn on Allow test builds to continue.Open Settings → Developer testing, turn on Allow test builds and physically confirm it. A CLI flag cannot enable it
test_execution_paused / This test is paused. Check Allow test builds.Physically turn Allow back on to resume approved tests; their code/data remain
test_owner_unknown / Jibo needs a linked owner to use test builds.Finish owner setup. If already set up, retain the code for support; do not edit identity files
test_native_collision, test_identity_collision / Remove “<installed app name>” first, then try again.Remove the named installed app through its supported flow. A new app ID is not global-name/port isolation
test_disk_limit / Jibo needs more space. Remove an unused test, then try again.Remove unused tests or free storage through supported tools
test_count_limit, test_project_limitOnly one skill test build can be installed; update the same project or remove that test before installing another. Removal retains the project record. Reuse allocation state rather than making new projects; there is no kit project-deletion command. Do not delete manager journals
test_queue_full, test_validation_busy, test_rate_limited, robot_install_busyInspect pending requests and let current work finish; do not repeatedly submit
test_input_changed / The build changed. Send it again and review the new request.Finish editing/copying; rebuild and send unchanged bytes
pack_changed, input_changed, artifact digest/size errorsRebuild once input is stable; check exact request status before retrying after a lost reply
client_request_conflictA retry ID refers to different content. Keep original state for an identical retry; changed bytes need a new build. A confirmed failed, canceled, declined or expired request retires the attempt; run install again for a fresh request and physical tap.
physical_tap_required, physical_approval_missing / Tap the button on Jibo’s screen to confirm.Use the real on-screen final confirmation. Scripts/voice/Agent cannot approve
test_approval_expired / This request timed out. Send the build again.Submit/review a fresh request; do not replay an old approval. Run install again; an explicit install after a confirmed terminal refusal creates a fresh request ID even with unchanged bytes.
test_request_stale / This request changed. Open Test builds again.Reopen the current request and review its actual content
native_health_failedMake health report readiness truthfully; inspect your bounded startup diagnostics
native_entry_invalidExport create(context) and all seven lifecycle methods
native_admission_closedstop has begun; clear existing handles, do not allocate a new context timer/hook/lease
native_cleanup_unconfirmedStop did not prove resource release. Fix view/speech/listen/socket/timer cleanup; do not return a success object early
native_lifecycle_timeoutStartup or stop exceeded its deadline. Bound work, cancel owned operations and do not block the event loop

If Allow changes after a request was queued, the CLI explains that the request stays queued until Allow is on and is canceled if Jibo restarts. It prints an exact ssh.mjs cancel command if you choose to cancel it. A queued request and an installed-but-paused test are different states.

If the CLI observes a confirmed failed, canceled, declined, or expired request, that attempt is retired. Run install again from the same project with the same connection options to create a fresh request ID and physical tap; the packed bytes can remain unchanged. This is different from a lost reply or timeout: read status first when the original request may still be live. For unexplained or persistent failures, keep the exact code and request ID for support.

It installed, but the skill looks wrong

SymptomCheck
No Home tileOn 13.8.0 a running local test's entries appear in Home after the Skill Store entries, prefixed LOCAL / Test — (see the local-test opening path). Open Home by touch and check runtimeState, registerLaunchers, getSetupState and pending changes. A background service intentionally has no tile
Tile says Set up …getSetupState returned configured:false; complete your own setup rather than hiding the state
Tap does nothingCurrent-view identity, ready/generation flag, inputLocked, component hit-area coordinates and visible button paint
Blank or covered screenPending transition, unsupported renderer features/assets, view ownership; do not remove a covering view that is not yours
Speech interrupts another activityApp-context lease and native speaker-session checks; no global speech stop without proven ownership
Listen never startsDid the prompt actually return SUCCEEDED? Is another local turn busy? Are voice services connected? followedByListen alone does not open a request
Wrong or late answerAccept only SUCCEEDED final ASR text, validate the word, and generation-check replies after close; hints are not an allowlist
Voice alias does nothingLocal v1 records claims but does not register aliases. Use the local-test opening path
Background API failsHTTPS/TLS/status, bounded response, timeout and endpoint compatibility. Do not disable TLS or retry forever
Port already in use (EADDRINUSE)Declared port/name collision and actual listener state. Choose a unique port and update incomingPorts as well as config
Cannot reach status service from a PCNetwork starter intentionally binds loopback. Read it from the robot's authorized shell; do not silently expose it on the LAN
Stop hangsPending request creation, owned listening cancellation, transition completion, open keepalive sockets and raw timers. Track and await each one
Counter opens on wrong pageReset page-local state on open; do not reuse state from a closed interaction unintentionally
An update loses settingsWrite to dataRoot, not appRoot; version your schema and keep malformed-data recovery separate from erase-data removal

The network starter's diagnostic strings are request_timeout, response_too_large, request_failed, response_failed, response_aborted, response_closed, request_aborted, service_config_invalid and service_stopped. These describe its own sample service, not new protocol errors. The voice starter rejects unconfirmed cancellation with voice_cancel_unconfirmed, even if the SDK has already completed the local request after a transport failure. That local state does not prove that the service acknowledged cancellation. The screen starters return native_view_unavailable before acquiring focus when the renderer is disabled. Hello-derived view errors (hello_close_timeout, hello_view_covered, hello_view_retained, hello_view_close_failed, hello_speech_busy) mean cleanup was not proven.

Details for support

Open a support ticket in #help on the Phoenix Discord: https://discord.gg/FyDVYQ6FfV. Include only a short diagnostic block, for example:

Command: install
Code: native_cleanup_unconfirmed
Stage: stop
Project version: 1.0.0
Request reference: [the exact request ID printed by your command]
Expected: the app closes and the test is removed
Observed: removal stopped with the code above

Keep credentials, pairing tokens, private source, account data, household names, photos, full inventories and unredacted logs out of public support messages. For the existing exhaustive named-code list, see the entry guide's error-code reference.