Skip to content

Commit 221758c

Browse files
committed
[docs] record existing Xcode account upload route
Signed-off-by: Viwat Vchirawongkwin <viwat.v@chula.ac.th>
1 parent 286d280 commit 221758c

1 file changed

Lines changed: 12 additions & 6 deletions

File tree

‎docs/developments/2026-q4-reliable-workflow/c1-s2/06_Release_Readiness.md‎

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -153,7 +153,8 @@ must use the actual delivered package.
153153
| Provisioning | Production App Store profile; debugging disabled, no development-device list, beta reporting enabled; valid through 17 May 2027 |
154154
| Validation | `tools/validate_ios_ipa.sh` passes code-signature, compiled minimum OS, embedded-asset mode/classification and Xcode `swinfo` checks; only the three expected unsigned resource-bundle records are excluded |
155155

156-
The archive and exported IPA are retained privately. A distribution package
156+
The archive (including dSYMs), exported IPA and Android R8 mapping are retained
157+
privately outside the temporary build worktree. A distribution package
157158
with no development-device list is not the separately installed development
158159
Preview app. Its local validation does not establish App Store processing,
159160
TestFlight availability, or store-installed upgrade behavior.
@@ -195,11 +196,16 @@ certificate. A valid Apple distribution identity and cached production App
195196
Store provisioning profile are available. Signing access alone does not prove
196197
an authenticated store session, role, account version history or review status.
197198

198-
No dedicated Play/App Store Connect connector or configured command-line store
199-
credential was found in the standard locations inspected. Account access and
200-
whether build 9 has already been consumed remain **unverified**. Read-only
201-
browser discovery did not establish an authenticated console session. This is not a
202-
claim that the owner has no access through the respective web consoles.
199+
No dedicated Play/App Store Connect connector or configured standalone
200+
command-line store credential was found in the standard locations inspected.
201+
However, Xcode preferences contain one configured production Apple-account
202+
reference, and its cached provisioning metadata includes the candidate signing
203+
team. The existing Xcode account may therefore support an archive upload after
204+
admission without a separate App Store Connect API key. Account metadata alone
205+
does not verify a live session, App Store Connect role or whether build 9 has
206+
already been consumed; these remain **unverified**. Read-only browser discovery
207+
did not establish an authenticated console session. This is not a claim that
208+
the owner lacks web-console access or that Xcode has no potential upload route.
203209

204210
After the candidate is admitted, the authorized distribution operator must
205211
verify the exact package, unused build numbers and current declarations, upload

0 commit comments

Comments
 (0)