addValue is excluded from ACTION_MAP by design — the note says WDIO fires it inside setValue, so mapping it would double-count. But that assumes it only ever appears nested. A direct addValue, which is idiomatic in Appium, then produces no action at all: the typing step is simply missing from the trace.
Seen on a real iOS run — a spec doing click → addValue → getText produced two action rows.
Worth noting the WDIO service already suppresses nested commands through its own command stack, so the exclusion may be redundant there. ACTION_MAP is shared with Selenium and Nightwatch, which have no equivalent, so this needs checking per adapter rather than just deleting the entry.
addValueis excluded fromACTION_MAPby design — the note says WDIO fires it insidesetValue, so mapping it would double-count. But that assumes it only ever appears nested. A directaddValue, which is idiomatic in Appium, then produces no action at all: the typing step is simply missing from the trace.Seen on a real iOS run — a spec doing click →
addValue→getTextproduced two action rows.Worth noting the WDIO service already suppresses nested commands through its own command stack, so the exclusion may be redundant there.
ACTION_MAPis shared with Selenium and Nightwatch, which have no equivalent, so this needs checking per adapter rather than just deleting the entry.