New
Introducing React Bench, see how different models perform on React code

react-doctor/rn-detox-missing-await

Prepend await to the Detox action, waitFor chain, or expect(element(...)) assertion: await element(by.id('submit')).tap()

Status
Active
Category
React Native
Assessment
Evidence-required risk
Required evidence
source code
Default configuration
Enabled
Default severity
warn
Show technical metadata
Scope
React Native
Active when
framework=react-native and capabilities=react-native
Requirements
react-native
Tags
react-native
Priority
42 (P3)
Source
oxlint-plugin-react-doctor
Rule set
oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
On this page

Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires only in Detox test files on a bare, un-awaited action, waitFor chain, or expect(element(...))/expect(web(...)) assertion. Element actions include tap, tapAtPoint, multiTap, longPress, longPressAndDrag, swipe, scroll variants, text-entry actions, pinch, pinchWithAngle, picker/accessibility/slider actions, getAttributes, and takeScreenshot. Suppress calls that are awaited or returned, matcher construction without an action, an element nested inside another awaited chain, and ordinary Jest expect. A promise chain is handled only when then/catch/finally supplies the completion or error behavior; an empty or dangling chain is not a safe substitute for await.

Evidence boundary

The diagnostic proves only that the detector’s modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

Record one outcome:

  • Confirmed failure: The required evidence establishes the violation.
  • Rejected: A documented exception or false-positive predicate applies.
  • Needs evidence: Named evidence can still be collected.
  • Unavailable: Required evidence cannot be collected in this run.
  • Waived with evidence: An authorized, scoped exception applies to an established failure.
  • Observation: The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review condition. It is not a pass or false positive.

Default severity is registry metadata. Use the occurrence’s JSON severity after repository configuration when ordering real findings.

Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Prepend await to the un-awaited Detox action, waitFor chain, or element/web assertion and make the enclosing test or step callback async. Preserve a returned promise or a then/catch/finally chain only when it genuinely propagates completion and failures to the test runner; do not retain an empty handler merely because its method name suppresses the detector.

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.

Show repository-wide prompt

Fix every confirmed react-doctor/rn-detox-missing-await diagnostic in the current repository.

Required change:

  • Prepend await to the un-awaited Detox action, waitFor chain, or element/web assertion and make the enclosing test or step callback async. Preserve a returned promise or a then/catch/finally chain only when it genuinely propagates completion and failures to the test runner; do not retain an empty handler merely because its method name suppresses the detector.

Validation before editing:

Fires only in Detox test files on a bare, un-awaited action, waitFor chain, or expect(element(...))/expect(web(...)) assertion. Element actions include tap, tapAtPoint, multiTap, longPress, longPressAndDrag, swipe, scroll variants, text-entry actions, pinch, pinchWithAngle, picker/accessibility/slider actions, getAttributes, and takeScreenshot. Suppress calls that are awaited or returned, matcher construction without an action, an element nested inside another awaited chain, and ordinary Jest expect. A promise chain is handled only when then/catch/finally supplies the completion or error behavior; an empty or dangling chain is not a safe substitute for await.

Constraints:

  • Make the smallest change that fixes the root cause.
  • Preserve behavior and interfaces unrelated to this diagnostic.
  • Reuse existing project components, utilities, and conventions.
  • Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
  • Before editing, inspect the manifest, lockfile, native app configuration, React Native and Expo versions, and New Architecture status.
  • Also inspect the Reanimated major, installed list-library majors, and every affected platform-specific file.
  • Do not add or upgrade a native dependency, change linking, or alter Pods/Gradle setup unless explicitly authorized.
  • Do not enable the New Architecture or change Expo/native configuration unless explicitly authorized.
  • Preserve navigation, gesture, keyboard, safe-area, accessibility, lifecycle, and platform semantics; do not treat them as file-local import substitutions.
  • Verify behavior in a release build on each affected device platform in scope. Name any unavailable platform instead of claiming it passed.
  • Adapt identifiers and framework details instead of copying blindly.
  • Do not disable the rule or suppress matching code.
  • Confirm this rule is enabled for the project: framework=react-native and capabilities=react-native.

Assessment:

  • Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
  • Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
  • A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:

  • Run focused tests for the changed behavior.
  • Run React Doctor and confirm this diagnostic no longer appears from changed code.
  • Run an unfiltered scan of the affected scope before claiming no cross-category regression.
  • Report the files changed and any checks you could not run.