Run an operator program on a new device before its first boot

未关闭
#1,202 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript
领域
tooling

调研方向

This is design work before it is code: the issue asks for an operator-supplied program to run on a new simulator or emulator before first boot, but names no file or entry point. Read the #327 spec and the iOS slim-before-first-boot spec in #1192 (ADR 0060) first, since the maintainer kept the rule that Simlock copies devices and runs no setup. Done means an agreed design for where the hook runs, how failures are reported, and which platforms it covers.

由索引模型根据 Issue 内容生成。

描述

request:new
The problem

An operator cannot have Simlock run a program of theirs on a new simulator or emulator before its first boot, for example a slimming step or settings written while the device is shut down, with failures reported. #1049 (point 2) asked for this. Named baselines (#327) cover the "prepare once" case by copying a device the operator prepared on a lease, and run no setup themselves, so a step that must happen before a device's very first boot, on every new device, has no place.

Who runs into this

Operators who want every new device, plain or from a baseline, changed by their own tool before it first boots, and who cannot do it on a lease because by then the device has booted.

What you would like to happen

From #1049: "An operator can run a program of their own on a new simulator before its first boot (a slimming step, settings), with failures reported."

Anything else

Split out of the #327 spec session on 2026-11-02: the maintainer kept #327's rule that Simlock copies devices and runs no setup, and asked for the hook as its own request. iOS slim before first boot is already specified in #1192 (ADR 0060). Related: #1049, #327.

Written by an agent.

主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。