Skip to content

[iOS 1.0] Prepare and preview the complete App Store product page and localized metadata #50

Open

Description

@HemSoft

Outcome

Prepare and preview the complete App Store product page and localized metadata.

Release tracker: [iOS 1.0] First App Store release tracker

Acceptance criteria

  • Write and version the app name, subtitle, promotional text, description, keywords, copyright, support URL, marketing URL, privacy URL, and applicable version/release text for every approved launch language.
  • Create a claim-to-evidence matrix like CodexBar's. Describe house-rule dice play, actual supported modes, offline behavior, accessibility, local history/high scores, and AI honestly. Do not imply standard licensed Yahtzee, official affiliation, online multiplayer, or cloud leaderboards without approved rights and implementation.
  • Validate Apple's current field lengths, localization rules, keyword restrictions, branding/content rules, URL behavior, categories, and device support. Avoid unsupported superlatives, placeholder text, or copied CodexBar wording.
  • Prepare accessibility nutrition-label responses only for support actually qualified on the relevant devices. Mark optional product-page features, accessibility URL, app preview, and promotional campaigns as included or explicitly deferred rather than mandatory boilerplate.
  • Sync the approved metadata to the correct app/version without submitting for review. Preview the App Store page for both iPhone and iPad, verify text and links, and coordinate final screenshot order with the screenshot issue.
  • Retain editable sources, a sanitized sync receipt, and a final owner copy review. Recheck privacy and age-rating consistency against the declared behavior.

Dependencies

Validation and completion

All mandatory product-page fields are filled, validated, and previewed in App Store Connect. Attach sanitized previews and a field/claim checklist tied to the release candidate.

Record the exact source revision, commands/artifacts, or sanitized App Store evidence as appropriate. Keep credentials and private contact/identity details out of this issue. Implementation changes must pass affected repository gates and receive review.

References

Activity

  1. added this to the iOS 1.0 milestone on Sep 27, 2026
  2. added
    documentationImprovements or additions to documentation
    iosiPhone and iPad app work
    app-storeApp Store release preparation and submission
    on Sep 27, 2026
  3. HemSoft commented on Sep 27, 2026

    @HemSoft
    CollaboratorAuthor

    Mission completion blocker

    The game's real App Store record, approved public/legal metadata and owner copy review.

    Evidence and two self-serve paths checked:

    1. Prepared editable English listing/review/release sources and a consistency guard in PR docs: prepare iOS release records and fail-closed candidate checks #56.
    2. Ran that guard and inspected the app-record/source inventory: app ID, approved name/copyright, live support/privacy/marketing URLs and native claim evidence are absent. A local draft is not an App Store Connect preview or a metadata sync receipt.

    Safe default: Retain explicit drafts and null fields; do not upload placeholder or trademark-dependent copy.

    Owner action: Complete #39/#43/#48/#49 and approve the final copy before an authorized App Store Connect sync/preview. Final product-page work is still pending.

    This is a blocker to this issue's full acceptance contract, not a claim that its unfinished implementation is complete. Repository-only preparation continues through the linked PRs; this issue stays open.

  4. HemSoft commented on Oct 1, 2026

    @HemSoft
    CollaboratorAuthor

    Updated acceptance blocker, October 1, 2026 EDT

    This supersedes the September 27 preimplementation assumptions. Native local saves/resume/UI, original development assets, unsigned CI and packaged privacy inspection are now delivered. The static companion site is prepared but unpublished. Screenshot and release/reporting preparation exists in the open PRs, not as accepted store material.

    Native foundation #57 and postmerge delivery, unpublished site #58, draft capture preparation #61, and draft release/reporting preparation #62. The last two PRs remain open; connected review capacity was explicitly refused on #61 and on #62. No purchase or substitute reviewer was used.

    Remaining need: Actual game App Store record and approved public/legal/localized listing copy and screenshots.

    Two self-service paths checked:

    1. Prepared English listing/review/release sources and source-review consistency checks in PR #56. PR #62 updates draft review behavior to the actual native implementation without representing shipment.
    2. Ran draft consistency and inspected candidate/listing sources plus issue43/49. App ID, approved public/copyright/category/contact/HTTPS fields and owner copy receipts are absent. A draft preview or fictionally preloaded capture is not an App Store Connect sync.

    Safe reversible result: Retain editable drafts and null fields. Do not upload placeholders or claim local copy has received owner review.

    Exact owner action: Complete issue #39/issue #43/issue #48/issue #49 approvals and authorize final copy review and App Store Connect metadata/preview verification.

    This issue remains open. Simulator, browser, fictional-fixture and unsigned evidence do not replace signed physical-device or legal/publication acceptance. CI waits and driver failures are still engineering work, not the owner block stated above. No credentials, private contacts or legal declarations are requested in this public issue.

  5. HemSoft commented on Nov 11, 2026

    @HemSoft
    CollaboratorAuthor

    Held: this step needs App Store Connect access for Third Roll, which the repository doesn't have and an agent can't obtain without a new login.

    Checked on 2026-11-11 (merge mission, Chief dispatch 022804d6):

    1. The repository has no Actions secrets or variables at all, so there is no App Store Connect API key, signing identity or team configuration to use.
    2. Even with an API key, the App Store Connect API can't create the app record; that is done in the App Store Connect website by the account holder. Every later step (metadata sync, screenshot upload, TestFlight, App Review, release) depends on that record. App Review submission also contacts Apple on the owner's behalf.

    The repository-side preparation for this item is on main (release records, metadata drafts, screenshot automation, privacy audit, unsigned archives). Nothing here spends money or needs a new account, but it does need Franz's App Store Connect session, so later sweeps should skip this issue until that access exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    app-storeApp Store release preparation and submissiondocumentationImprovements or additions to documentationiosiPhone and iPad app work

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions