Issues

iOS `SecureEnclaveSecureArea.getKeyInvalidated` always returns `false`, so key invalidation is undetectable on iOS

#1952

· mc1100 opened

on Aug 25, 2026

`requestCredentials`: rotated authorization data is persisted only on the branch that actually fetched credentials

#1951

· mc1100 opened

on Aug 25, 2026

No public API to re-authorize provisioning into an existing `Document` — `ProvisioningModel.launch`'s coroutine context cannot be constructed outside the library

#1950

· mc1100 opened

on Aug 25, 2026

`uriSchemePresentment`: the verifier's error response body is discarded by a bare `check(...)`

#1949

· mc1100 opened

on Aug 25, 2026

OpenID4VCI: deferred issuance is unreachable — `202 Accepted` is treated as an error, `deferred_credential_endpoint` is never parsed, and the token/DPoP key are not exposed

#1948

· mc1100 opened

on Aug 25, 2026

OpenID4VCI: `authorization_details` is sent to authorization servers that do not advertise support for it, failing the pushed authorization request

#1947

· mc1100 opened

on Aug 25, 2026

`SdJwtVcCredential.getClaimsImpl` returns JWT envelope claims (`iss`, `cnf`, `vct`, `exp`, `_sd_alg`) as document claims

#1946

· mc1100 opened

on Aug 25, 2026

`CredentialMetadata` drops `credential_metadata.claims[]`, so wallets cannot show the issuer's published claim names

#1945

· mc1100 opened

on Aug 25, 2026

test, and verify multipaz skills

#1942

· VishnuSanal opened

on Aug 24, 2026

OpenID4VCI: client-attestation challenge not refreshed for authorization_code, never fetched for refresh_token → 401 invalid_client

#1933

· mc1100 opened

on Aug 21, 2026

[Feature Request] Allow toggling of torchlight in QrCodeScanner composable

#1932

· kenneth-leong-gt opened

on Aug 20, 2026

Better documentation for VerifiedPresentation and PresentmentRecord

#1921

· davidz25 opened

on Aug 17, 2026

Navigation Menu

Uh oh!

All issues

iOS `SecureEnclaveSecureArea.getKeyInvalidated` always returns `false`, so key invalidation is undetectable on iOS

`requestCredentials`: rotated authorization data is persisted only on the branch that actually fetched credentials

No public API to re-authorize provisioning into an existing `Document` — `ProvisioningModel.launch`'s coroutine context cannot be constructed outside the library

`uriSchemePresentment`: the verifier's error response body is discarded by a bare `check(...)`

OpenID4VCI: deferred issuance is unreachable — `202 Accepted` is treated as an error, `deferred_credential_endpoint` is never parsed, and the token/DPoP key are not exposed

OpenID4VCI: `authorization_details` is sent to authorization servers that do not advertise support for it, failing the pushed authorization request

`SdJwtVcCredential.getClaimsImpl` returns JWT envelope claims (`iss`, `cnf`, `vct`, `exp`, `_sd_alg`) as document claims

`CredentialMetadata` drops `credential_metadata.claims[]`, so wallets cannot show the issuer's published claim names

test, and verify multipaz skills

OpenID4VCI: client-attestation challenge not refreshed for authorization_code, never fetched for refresh_token → 401 invalid_client

[Feature Request] Allow toggling of torchlight in QrCodeScanner composable

Better documentation for VerifiedPresentation and PresentmentRecord

Uh oh!

Search results