fix(ios): system-surface disclosure parity across selector routes
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- ios, typescript
Research direction
Start with the shared selector response builder and the existing withSystemSurfaceDisclosure helper, then compare the iOS selector routes (get, is, find, and wait) with the Android systemSurfaceDisclosure pattern. Add a parity test covering those routes against a served sheet; done means every route includes the disclosure from system-surface provenance.
Written by the indexing model from the issue text.
Description
Follow-up to #2438 / #2448.
Purpose. The system-surface disclosure currently rides the snapshot warnings. Ensure it also surfaces on selector-backed routes (find/wait/get/is), matching the Android systemSurfaceDisclosure pattern, so the disclosure cannot silently drop on one route while surviving on another.
Required behavior. Route the disclosure through the shared selector response builder keyed off the capture's system-surface provenance (generalize withSystemSurfaceDisclosure), rather than only the direct snapshot warning path.
Observable completion. get/is/find/wait against a served sheet include the disclosure; a test asserts parity across routes.
Dependencies. #2448 (provenance + snapshot disclosure landed).
- Dominant language
- TypeScript
- Stars
- 4.8k
- Forks
- 315
- Avg merge
- 11h 8m
- Merged PRs (30d)
- 551
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from callstack/agent-device
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
callstack/agent-device#3062 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
callstack/agent-device#1869 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
callstack/agent-device#3106 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
callstack/agent-device#3105 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
callstack/agent-device#3104 ·
Maintainers usually reply within 1 day
All issues in callstack/agent-device
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
betagouv/mon-entreprise#4699 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
ai-driven-qa
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1467 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
need4deed-org/sdk#267 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
auth0/universal-login#414 ·
Maintainers usually reply within 1 day