Skip to content

Tech debt: replace the wallet APK link with the Multipaz release on apps.multipaz.org #472

Open

Description

@dzuluaga

In plain terms

To sign a spending grant on a phone, the docs (#470) link a Multipaz Wallet APK we built ourselves from unmerged pull requests. That's a stopgap: developers install a file from us instead of the wallet Multipaz publishes. Once Multipaz releases a wallet that signs AP2's delegate request, the docs should say "install Multipaz Wallet from apps.multipaz.org" and the APK link goes away.

Part of #464.

Why it's an APK today

The wallet (openwallet-foundation/multipaz-wallet#48) depends on Multipaz 0.103.0-SNAPSHOT plus two unmerged library changes, openwallet-foundation/multipaz#2178 (the delegate request) and openwallet-foundation/multipaz#2196 (its consent screen). No published snapshot has them, so building it means publishing #2196 to mavenLocal first. Writing that up for developers was too much for a stopgap.

Unblocked by

  1. Support AP2 spending mandates delegated over OpenID4VP. openwallet-foundation/multipaz#2178 merged
  2. Draw AP2 spending permissions with default renderers in the SDK. openwallet-foundation/multipaz#2196 merged
  3. Show AP2 spending permissions in the consent prompt. openwallet-foundation/multipaz-wallet#48 merged
  4. A wallet release on apps.multipaz.org that includes them

Acceptance criteria

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

    documentationImprovements or additions to documentation

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions