Arcane OS Docs Development only

Reference

Arcane.system.ping()

Confirms only that the bound host bridge admitted and answered the request. It does not claim dependency readiness, system health, privilege, signer trust, or release-candidate status.

  • Reference

This focused page is derived from the mechanically checked full member inventory.

Syntax

Arcane.system.ping()

Parameters

None

Return value

Promise<{ok:true}>

Description

Confirms only that the bound host bridge admitted and answered the request. It does not claim dependency readiness, system health, privilege, signer trust, or release-candidate status.

Overview

Arcane.system.ping() confirms that the bound Arcane bridge admitted and answered one request. It requires no capability and is available on Core and Android. It uses a 10-second client timeout, has no side effect, and emits no event.

Result and limits

The exact result is {ok: true}. Success does not prove installation health, network reachability, renderer readiness, dependency readiness, elevation, publisher trust, signing, or release-candidate status. Use the focused status method for each of those questions.

Errors and recovery

ARCANE_TRANSPORT_UNAVAILABLE means no host is connected. ARCANE_REQUEST_TIMEOUT means the bridge did not complete before the client deadline. Android can reject duplicate or invalid bridge frames. Treat any failure as an unknown bridge state and reconnect; do not turn it into a broader health diagnosis without evidence.

Example

const reply = await Arcane.system.ping();
console.log('Bridge replied', reply.ok);

Reference group

Platform, installation, users, and system

Repository and reviewed source access