Upload a folder or a build once for many leases, and put files into an app's container

Offen
#1,636 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
20/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
android, ios, typescript
Bereich
backend, mobile-dev

Rechercherichtung

Read the linked request #945, lease files issue #1351, and ADR 0067 for the current upload model and its limits. The issue leaves storage scope, retention, permissions, archive unpacking, and iOS and Android container access as open design questions. Done means those behaviors are specified and a CI run can reuse one build across leases and place fixtures in each app's data container.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

feature:spec

Request: #945

Problem

A lease's files (#1351) belong to one lease, so a run that installs the same build on many leases uploads it once per lease. budgie's e2e suite (budgie-at/budgie#1867, from the comment on #945) uploads the same .app through the gateway for each of 10 leases. Requests past 100 s end in a Cloudflare 524, so it uploads at most 3 at a time, and about 4 of the run's 15 minutes are setup.

There is also no way to put files into an app's data container. budgie built a helper simulator app (E2EDrop) and sends fixtures as base64 raw-deflate on exec stdin, unpacked with simctl spawn <helper> untar <dir>.

A lease file is one flat file, and nothing unpacks an archive (ADR 0067: "Unpacking an uploaded archive into folders (an iOS .app) … not in this decision"). A simulator .app is a folder, so a remote caller cannot install an iOS app it built from the lease folder at all. #1635 (remote CLI) ships single-file uploads and leaves this here, decided in its spec session of 2026-11-17.

Who it is for

A CI run that installs one build on many leased devices, and puts test fixtures into the app on each.

Open questions

  • How a folder (an iOS .app) reaches the lease folder: simlock files put ./MyApp.app packs it and the worker unpacks it, or an archive upload is unpacked on request.
  • Where a shared upload lives (per token, per run, per gateway or worker), how long it is kept, and who may install from it.
  • How a file reaches an app's data container, on iOS and on Android.

Written by an agent.

Vorherrschende Sprache
TypeScript
Sterne
705
Forks
40
Ø Merge
12 Std. 9 Min.
Gemergte PRs (30 T.)
376

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus callstackincubator/simlock

Alle Issues in callstackincubator/simlock

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.