Skip to content

Validate TestFlight packaging and App Store icon separately #71

@cbusillo

Description

@cbusillo

Objective

Keep TestFlight packaging/icon validation separate from runtime/provider bugs so App Store Connect issues do not blur with local dogfood behavior.

Finish Line

The archive/upload path includes the expected app icon assets, entitlements, embedded provisioning profiles, and bundle metadata, and any App Store Connect icon issue has package/archive evidence.

Current Status

State: Active
Next action: After runtime/provider stabilization, inspect the generated archive/pkg/zip upload artifact rather than the running app bundle alone.
Blocked by: Runtime recovery and dirty-tree triage.
Last verified: 2026-05-12 installed app contained AppIcon.icns, Assets.car, and CFBundleIconName=AppIcon, but ASC behavior still needed upload-path inspection.

Scope

  • In: TestFlight packaging, icon asset inclusion, Info.plist icon metadata, provisioning profiles, entitlements, upload validation.
  • Out: Provider runtime failures and settings UI regressions.

Acceptance Criteria

  • Upload artifact contains expected icon resources and Info.plist keys.
  • App, widget, and refresh agent profiles/entitlements match App Store requirements.
  • TestFlight upload validation is run only from a coherent release branch/build.
  • App Store Connect icon finding, if still present, has artifact-level evidence.

Relationships

Sub-issue of #64.

Validation

Inspect the generated upload artifact, not just /Applications, and run the configured TestFlight packaging/upload validation path.

Decisions

Installed app icon presence is necessary but not sufficient evidence for ASC.

Open Questions

Is ASC missing the icon because of the archive/pkg/upload path, asset catalog compilation, or metadata processing delay?

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions