Skip to content

Blocker: signed iOS device install and share-transfer UAT needs macOS hardware #158

Description

@dskvr

MeshDrop has iOS native-source, simulator app, unsigned device package, share extension, share-inbox bridge, and signed-device harness plumbing, but final signed iOS device UAT remains unproven without macOS signing hardware and a real device.

Current evidence in GSD:

  • iOS source and simulator artifacts build.
  • Signed device-install harness exists and launches through devicectl when signing/device prerequisites are present.
  • Share extension stages files into the app group and web code consumes meshdropShareInbox.
  • Real signed hardware install/share-transfer UAT remains open.

Required unblocker:

  • Provide macOS host with Xcode signing identity/provisioning and a connected iOS device.
  • Run the signed iOS device-install harness against the current release/source.
  • Exercise file picker/share sheet ingress and an actual MeshDrop transfer proof from the signed installed app.

Acceptance:

  • Signed app installs and launches on real iOS hardware.
  • Share sheet or picker ingress puts a real file into MeshDrop send flow.
  • Transfer proof includes iOS runtime, route type, bytes sent/received, hash match, and fallback status.
  • Harness failure modes stay explicit for missing signing identity, no device, or provisioning mismatch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions