Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

settings permission --app writes a display name as the bundle id instead of resolving it

Aperta
  • Qualcosa non va?
#3,384 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@thymikee ci sta già lavorando.

Dal 10/10/2026.

  • #3386 di @thymikee — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
android, ios, typescript
Ambito
cli, mobile-dev

Direzione di ricerca

Start from how settings clear-app-state --app resolves a display name to a bundle id, then check where settings permission and iOS location pass app straight to simctl privacy or pm grant/pm revoke. Done when a display name reaches those calls as its resolved id, an unknown app is refused with details.dispatched: 'no', and tests cover both platforms. Open PR #3386 already targets this, so check it before starting.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem

settings permission … --app <name> (#3179) passes the app through unresolved. On iOS it goes straight to simctl privacy; on Android it goes to pm grant or pm revoke. A display name is never resolved to its bundle id or package. settings clear-app-state --app, open and close all resolve it.

Live on 0.21.22 (iOS 27.1 simulator):

agent-device settings permission grant photos --app Maps --platform ios --udid <udid>
# Updated setting: permission

The simulator's TCC.db then has a kTCCServicePhotos row for client Maps, not com.apple.Maps. The real app never gets the permission, and the command reports success. settings clear-app-state --app Maps on the same device resolves to com.apple.Maps ("bundleId": "com.apple.Maps").

Consumer impact: tester-army/e2e pins apps by whatever app accepts, including display names (its quickstart uses bundleId: 'Settings'). To drop its "open the app first so the session names it" workaround, it needs --app on permissions to accept what open --app accepts.

Required behavior

  • An app-scoped settings mutation (permission, and iOS location grant/revoke) resolves an explicit app the way clear-app-state does: a bundle id or package passes through, and a display name resolves to the installed app's id.
  • An app that resolves to nothing is refused before anything is sent, with details.dispatched: 'no'. It is never written as a literal client id.

Done when

  • Tests on both platforms: a display name resolves to the id that reaches simctl privacy or pm, and an unknown app is refused.
  • Live on an iOS simulator: settings permission grant photos --app Maps writes the TCC.db row for com.apple.Maps.

Related: #3179.

Lingua principale
TypeScript
Stelle
4.9k
Fork
328
Merge medio
12h 18m
PR unite (30g)
538

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.