Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mobile signing prompts do not show whose account is being used

Open
  • Is something wrong?
#998 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
kotlin, swift
Domain
mobile-dev

Research direction

Start with TrUAPIReviewPromptMapper.swift and ConfirmationReviewMapping.kt, then compare their handling of callingProductId with the host-cli rendering. Trace the signing review payloads into TrUAPIConfirmation.Signing and StatementSignConfirmationRequest. Done means iOS and Android show both caller and owner, and identify when the products differ.

Written by the indexing model from the issue text.

Description

bug host-android host-ios host-work

A product granted context can sign with another product's account (#873). The user confirming that signature is meant to see both names. On iOS and Android they see one.

  • iOS TrUAPIReviewPromptMapper.makeStatementSignRequest takes the requester from review.account.dotNsIdentifier, which is the account owner, not the caller. A cross-product statement sign names the wrong product.
  • Android ConfirmationReviewMapping takes the caller from the connection and never shows the owner.
  • Both ignore the callingProductId that #873 added to SignPayloadReview, SignRawReview, CreateTransactionReview and StatementStoreProductSignReview.

The host-cli renders both, so the behaviour is specified and only the two signing hosts are missing it.

Fix

Carry the owner alongside the caller into TrUAPIConfirmation.Signing and StatementSignConfirmationRequest, and say in the sheet when they differ.

  • hosts/ios/polkadot-app/Modules/Products/TrUAPI/Confirmation/TrUAPIReviewPromptMapper.swift
  • hosts/android/feature/products/impl/src/main/java/io/paritytech/polkadotapp/feature_products_impl/domain/truapi/ConfirmationReviewMapping.kt
Dominant language
Swift
Stars
10
Forks
3
Avg merge
1d 9h
Merged PRs (30d)
211

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from paritytech/host-rust-core

All issues in paritytech/host-rust-core

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.