You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8bc84c2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(harmonyos): refuse the trajectory carrier by default and name the transport in results
Motivation:
Integration smoke on a slider page caught the carrier path reporting a green
injection that moved nothing: same slider, same coordinates, `uitest uiInput
swipe` triggered the ArkUI PanGesture 3/3 while the carrier injected 0/4 across
every shape (2-point line, fine steps, burst) - its touches reach system-layer
windows but not component-anchored gestures of ordinary app windows.
Approach:
- the human-trajectory lowering takes the raw evdev sendevent transport first;
when the device denies it, `--trajectory human` refuses with
trajectory-channel-unavailable (comparison data in the message) instead of
reporting a silent green.
- the carrier becomes an explicit operator opt-in behind
AGENT_DEVICE_HARMONY_CARRIER=1, with a missing carrier refusing via its typed
error, and results carry trajectoryTransport so callers can negotiate.
Test evidence:
- on-device comparison runs recorded in examples/harmony-trajectory-driver/README.
- 858 contracts+platform-harmonyos unit tests, including the refusal-instead-
of-green cells for denied listings and missing carriers.
Co-Authored-By: Claude Code <noreply@anthropic.com>
'No effective HarmonyOS trajectory transport on this device (comparison runs: uiInput triggered 3/3, carrier 0/4)',
100
+
{
101
+
reason: 'trajectory-channel-unavailable',
102
+
hint: 'Raw evdev is denied by this build and the carrier HAP route does not reach component-anchored gestures. Set AGENT_DEVICE_HARMONY_CARRIER=1 to force the experimental carrier path, or run the endpoint swipe transport.',
0 commit comments