Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

iOS reliability follow-ups from v0.21.5–v0.21.8 review

Closed
  • Is something wrong?
#2,725 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
ios, typescript
Domain
mobile-dev, testing-qa

Research direction

Read the linked child issues #2726–#2731 and their blockers before starting; this issue is coordination rather than a single implementation task. Check each child’s acceptance tests, stopping condition, and implementation or evidence PR, then verify all child states and required live semantic evidence. Do not add CI wiring for #2731 or guess unresolved API behavior.

Written by the indexing model from the issue text.

Description

enhancement needs-triage

Purpose

Track bounded follow-ups from the v0.21.5–v0.21.8 iOS source review and the measured iPhone Duo investigation in #2724. This is coordination, not a single implementation PR. Existing input bugs #2711 and #2719 remain linked to #2724; #2694 remains the separate disclosure-routing task.

Execution contract

Each child is deliberately sized for Luna: concrete entry files, one outcome, explicit exclusions, acceptance tests, and a stopping condition. Work one issue per PR. Read blockers before starting; needs-triage children are not AFK-ready. Do not implement an unresolved API/behavior choice by guessing. Investigation success means evidence and a decision, not speculative production code.

Child tasks

  • #2726 — fix(ios): correct targetActivation background-state decoding
  • #2727 — investigate(ios): establish a measured screen-capture source for the active window
  • #2728 — fix(ios): use the resolved display for screenshots and visual verification
  • #2729 — fix(fold): make reported screen dimensions match their coordinate-space contract
  • #2730 — fix(fold): distinguish an observed half-open angle from a settled pose
  • #2731 — test(ios): automate semantic checks across Duo pose transitions

Order and resolved decisions

The display-capture investigation #2727 is complete with measured open/half-open/closed, single-panel, and native-alert evidence. #2728 adopts resolved-window capture with upright raster encoding and actual scale; implement on #2724 or after its merge. #2729 retains released dimensions and marks them coordinateSpace: "native-panel". #2730 requires stable half-open readings and distinguishes unsettled failure. These decisions are recorded in the child contracts.

#2731 is explicitly local-only by maintainer decision until GitHub Actions supports Duo. It can be implemented on #2724 and does not depend on the screenshot or metadata fixes. Automatic CI wiring is deferred, not a completion condition. All four implementation tasks are ready with their branch prerequisites explicit.

Completion

Verify all child issue states and their implementation/evidence PRs, not just this checklist. Runtime changes require live semantic evidence; mocked unit tests and successful synthesis acknowledgements are insufficient. Keep the existing centralized response decoding, typed lifecycle/readiness work, and off-deadline bridge preparation; no broad rewrite is requested.

Dominant language
TypeScript
Stars
4.8k
Forks
315
Avg merge
11h 37m
Merged PRs (30d)
556

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from callstack/agent-device

All issues in callstack/agent-device

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.