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

iOS/Android: present the credential-endpoint permission instead of refusing it

Open
#797 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
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, rust, swift

Research direction

Trace Products.RemotePermissionRequest, ProductPermission, toDomainRequest(), RustProductExecutionBridge.remotePermission, and Android's ProductPermission.fromLocal. Done means iOS presents a method/path/domain-specific credential prompt and accepts the permission, while Android can restore a stored credential grant without reporting an unknown type.

Written by the indexing model from the issue text.

Description

host-work

#781 adds RemotePermission::Credential { domain, path, method } (RFC 0025). iOS currently refuses it: toDomainRequest() answers nil and RustProductExecutionBridge.remotePermission returns false, so a product asking for a credential endpoint is declined on this host.

That was the safe way to unbreak the build — the permission is the prompt, since it attaches a host-derived caller identity to an outbound request, and there is nothing to show the user yet.

Full support needs:

  • a credential(domain:path:method:) case on Products.RemotePermissionRequest, plus its Tag and from(json:) arm
  • a ProductPermission case carrying domain, path and method, so the guard can store a decision per endpoint rather than per domain
  • prompt copy that names the method, path and domain, and says an identity is attached — the grant is GET /x on one host, not the host
  • toDomainRequest() returning it instead of nil, and dropping the refusal in remotePermission

Android needs the same separately: it maps persisted permissions by type name (ProductPermission.fromLocal) and will error("Unknown permission type: …") on a stored credential grant once one can exist.

Dominant language
Swift
Stars
10
Forks
3
Avg merge
1d 12h
Merged PRs (30d)
201

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.