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

Ouverte
#1,636 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
android, ios, typescript
Domaine
backend, mobile-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
705
Forks
40
Merge moyen
12 h 9 min
PR mergées (30 j)
376

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstackincubator/simlock

Toutes les issues de callstackincubator/simlock

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.